dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-23806

HIGH · 7.1 CVSS v3.1 Published 2025-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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
Cross-Site Request Forgery (CSRF) vulnerability in ThemeFarmer Ultimate Subscribe ultimate-subscribe allows Reflected XSS.This issue affects Ultimate Subscribe: from n/a through <= 1.3.

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

Cross-Site Request Forgery (CSRF) vulnerability in ThemeFarmer Ultimate Subscribe plugin (versions <= 1.3) allows attackers to trick authenticated users into performing unintended actions. The vulnerability enables Reflected XSS, where malicious scripts can be injected through crafted links and executed in the victim's browser when they interact with the vulnerable endpoint.

MitigationImplement anti-CSRF tokens (nonces) on all form submissions and state-changing operations in the plugin, and apply proper input sanitization and output encoding to prevent the reflected XSS vector.

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

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/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. Locate plugin version
    Navigate to WordPress admin > Plugins > Installed Plugins > ThemeFarmer Ultimate Subscribe and note the version number displayed
    Affected if the version listed is 1.3 or lower
  2. Confirm plugin is active
    In the same plugins list, verify the plugin has the 'Active' status indicator enabled
    Affected if the plugin is currently active and version is 1.3 or lower
  3. Identify vulnerable form endpoints
    Inspect the plugin files (typically in wp-content/plugins/ultimate-subscribe/) for form handlers that process user input without checking a nonce or token
    Affected if form processing files contain actions without wp_nonce_field() or wp_verify_nonce() calls
  4. Check for reflected XSS sink
    Review the plugin code for output functions (echo, print, etc.) that directly reflect request parameters without sanitization (esc_attr(), esc_html() or similar)
    Affected if user-supplied parameters are echoed back to the browser without encoding and the plugin is active in version 1.3 or lower

You are affected if the ThemeFarmer Ultimate Subscribe plugin is active at version 1.3 or lower and lacks anti-CSRF nonce validation on form submissions that reflect user input back to the browser.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all form submissions and state-changing operations in the plugin, and apply proper input sanitization and output encoding to prevent the reflected XSS vector.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23806 — 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-23806 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