CVE-2025-47639
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Supertext Supertext Translation and Proofreading polylang-supertext allows Stored XSS.This issue affects Supertext Translation and Proofreading: from n/a through <= 4.26.
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 · moderate confidenceA CSRF vulnerability in the Supertext Translation and Proofreading polylang-supertext plugin (versions up to 4.26) allows attackers to inject malicious scripts via Stored XSS by tricking authenticated users into triggering crafted requests.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify polylang-supertext plugin is installedCheck for the plugin directory at wp-content/plugins/polylang-supertext/ or search for 'Supertext Translation' in WordPress admin under Plugins > Installed PluginsAffected if The plugin appears in the installed plugins list
-
Check installed plugin versionView the plugin version in the WordPress admin plugin list, or inspect wp-content/plugins/polylang-supertext/readme.txt or the main plugin PHP file for the 'Version' header commentAffected if The version number is 4.26 or lower, or no version is displayed (indicating an old unversioned release)
-
Confirm WordPress user authentication is enabledCheck WordPress admin > Settings > General > 'Membership' setting (or inspect wp_options table for 'users_can_register' value)Affected if Either 'Anyone can register' is enabled, or the site has existing user accounts that could be tricked into triggering requests
-
Identify state-changing plugin features in useReview admin menu for Supertext Translation submenu items (usually under Settings or Tools), note any forms or actions for managing translations, proofreading orders, or language configurationsAffected if The plugin features are actively configured or used on the site
-
Test for missing CSRF protection on plugin actionsSubmit a crafted form to the site admin without a valid nonce token using a tool like Burp Suite or by inspecting page source for '_wpnonce' or '_wp_http_referer' parameters in plugin formsAffected if Plugin forms submit without requiring a nonce token, or the nonce can be omitted without rejection
A site is affected if the polylang-supertext plugin is installed with version 4.26 or lower, users can authenticate to WordPress, and the plugin handles form submissions without verifying CSRF tokens.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement anti-CSRF tokens (nonces) on state-changing operations and update to a patched version when available; validate and sanitize all user inputs to prevent XSS.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47639 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47639 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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