WordPress Hash Form plugin <= 1.4.0 - Cross Site Request Forgery (CSRF) vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps HashThemes/Hash Form (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for HashThemes/Hash Form.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 24, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 24, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 24, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress Fluent Support Pro plugin <= 2.3.1 - Cross Site Request Forgery (CSRF) vulnerabilityAlso CWE-352
• HCL Hive is affected by use of a cryptographic primitive with a risky implementationSame generic ecosystem
• HCL Hive is affected by a broken access control vulnerabilitySame generic ecosystem
• HCL Hive is affected by an information exposure vulnerabilitySame generic ecosystem
• WordPress Tonda theme < 2.6 - Local File Inclusion vulnerabilitySame generic ecosystem
• WordPress Tonda Core plugin < 2.6 - Local File Inclusion vulnerabilitySame generic ecosystem