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

CVE-2025-52789

HIGH · 7.1 CVSS v3.1 Published 2025-06-20
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 George Lewe Lewe ChordPress chordpress allows Stored XSS.This issue affects Lewe ChordPress: from n/a through <= 4.0.1.

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 Lewe ChordPress allows attackers to forge requests that inject malicious JavaScript (Stored XSS) into the database. When other users view the injected content, the attacker's script executes in their browser, enabling session hijacking, credential theft, or defacement.

MitigationImplement WordPress nonces on all form submissions and AJAX endpoints to prevent CSRF attacks. Sanitize and escape all user-supplied input before storing and rendering to prevent the stored XSS component.

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. Verify ChordPress plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ChordPress' or 'Lewe ChordPress' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active - only active plugins can process form submissions and render stored content that could contain malicious scripts.
  2. Check installed ChordPress version
    In WordPress admin, go to Plugins > Installed Plugins, find ChordPress, and note the version number displayed. Alternatively, check the plugin's main PHP file (usually wp-content/plugins/chordpress/chordpress.php or similar) for the 'Version' header in the plugin comment block.
    Affected if The installed version is any version prior to the patched release - CVE-2025-52789 affects ChordPress versions lacking CSRF nonce protection on forms and AJAX endpoints.
  3. Inspect ChordPress database tables for unexpected content
    Access the WordPress database (via phpMyAdmin or command line) and query tables that store ChordPress data (typically wp_posts with chordpress post_type or a custom table). Look for any records containing script tags, iframe tags, or javascript: URIs in content fields.
    Affected if Malicious script tags or event handlers (onerror, onload, onclick) are found stored in ChordPress-related database records, indicating successful XSS injection via the CSRF vulnerability.
  4. Review server access logs for forged requests
    Examine web server access logs (Apache, Nginx) for POST requests to ChordPress AJAX endpoints or form handlers that lack proper CSRF token validation. Look for requests without WordPress nonces or with predictable/invalid nonce values.
    Affected if POST requests to ChordPress endpoints are found that do not include a valid 'nonce' parameter or WordPress security token in the request body or headers.
  5. Check browser console for XSS errors when viewing ChordPress content
    Navigate to any ChordPress-rendered page on the site while browser developer tools are open (F12). Inspect the Console tab for any executed XSS payloads or CSP violation messages.
    Affected if JavaScript code executes unexpectedly or CSP blocks are triggered when loading ChordPress content, confirming stored XSS is present.

You are affected if Lewe ChordPress plugin is active, any version is installed, and either malicious script tags exist in the database or AJAX/form endpoints lack CSRF nonce validation.

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 WordPress nonces on all form submissions and AJAX endpoints to prevent CSRF attacks. Sanitize and escape all user-supplied input before storing and rendering to prevent the stored XSS component.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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