dbcve.org
SureformsWordPress extension · Brainstormforce

CVE-2025-5921

MEDIUM · 5.8 CVSS v3.1 Published 2025-08-01
Fix available
A fix is available. Upgrade to 1.7.2 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The SureForms WordPress plugin before 1.7.2 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting which could be used against both authenticated and unauthenticated users.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The SureForms WordPress plugin before version 1.7.2 contains a reflected Cross-Site Scripting (XSS) vulnerability due to failure to properly sanitize and escape a user-controlled parameter before outputting it back into the page, allowing injection of malicious JavaScript.

MitigationUpdate SureForms plugin to version 1.7.2 or later which includes proper input sanitization and output escaping.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SureformsWordPress extension
Affected:< 1.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm SureForms plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'SureForms' by Brainstormforce in the list.
    Affected if SureForms plugin is not found in the plugins list, the system is not affected.
  2. Identify installed SureForms version
    In the WordPress admin, go to Plugins > Installed Plugins. Find SureForms and locate the version number displayed beneath the plugin name.
    Affected if The version displayed is less than 1.7.2 (for example, 1.7.1, 1.7.0, 1.6.x, etc.).
  3. Verify version via file inspection
    If accessible, check the main plugin file (usually /wp-content/plugins/sureforms/main.php or similar) for the 'Version' header in the plugin comment block.
    Affected if The version header in the plugin file shows a version number lower than 1.7.2.
  4. Check if vulnerable parameter is processed
    Review HTTP requests to the site for any parameters being reflected back in the response without encoding. Common reflected XSS indicators include seeing your input appear verbatim in HTML source.
    Affected if User-supplied parameters from the URL query string are reflected in the page output without proper HTML encoding.

A system is affected if the SureForms plugin by Brainstormforce is installed with a version lower than 1.7.2, as the plugin fails to sanitize user-controlled parameters before reflecting them into the page.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.2 or later
Fixed in 1.7.2
Interim mitigation

Update SureForms plugin to version 1.7.2 or later which includes proper input sanitization and output escaping.

Recommended fix High confidence

SureForms version 1.7.2

  1. Backup the WordPress site database and files before making any changes
  2. Navigate to WordPress Admin Dashboard > Plugins > Installed Plugins
  3. Locate SureForms in the plugin list and click 'Update Now' to upgrade to version 1.7.2
  4. Alternatively, download SureForms version 1.7.2 from the WordPress Plugin Repository and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version shows 1.7.2 or higher in the installed plugins list
  6. Test that forms created with SureForms function correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sureforms Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5921 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data