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

CVE-2025-23577

HIGH · 7.1 CVSS v3.1 Published 2025-01-16
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 Sourov Amin Word Freshener word-freshener allows Stored XSS.This issue affects Word Freshener: 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 · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the Word Freshener WordPress plugin (versions <= 1.3) enables attackers to trick authenticated administrators into unknowingly submitting malicious requests that result in Stored XSS. The lack of proper CSRF token validation on plugin forms allows attackers to craft forged requests that inject malicious scripts into the affected pages.

MitigationImplement WordPress nonces (CSRF tokens) on all form submissions and AJAX actions, and ensure all user-supplied data is properly sanitized before output using WordPress sanitization functions like esc_html() and esc_attr().

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 Word Freshener plugin is installed
    Navigate to WordPress admin > Plugins and locate the Word Freshener plugin, or inspect the plugin directory at /wp-content/plugins/word-freshener/ for the main PHP file
    Affected if The plugin is installed and active in WordPress
  2. Determine installed plugin version
    Check the plugin header in the main PHP file (e.g., word-freshiner.php) for the Version field, or view the version in the WordPress Plugins admin page
    Affected if Version number is 1.3 or lower (e.g., 1.3, 1.2, 1.1, 1.0)
  3. Inspect plugin forms for CSRF token implementation
    Examine the plugin PHP files for presence of WordPress nonce functions such as wp_nonce_field(), wp_nonce_url(), or check_admin_referer() on form submissions
    Affected if Forms exist but no nonce verification is found (no wp_nonce_field or check_admin_referer calls)
  4. Check AJAX actions for nonce verification
    Search plugin code for admin-ajax.php handlers or do_action('wp_ajax_') hooks and verify if they include nonce checks using check_ajax_referer() or wp_verify_nonce()
    Affected if AJAX actions exist but lack nonce verification

If the Word Freshener plugin version is 1.3 or lower AND forms/AJAX actions lack nonce verification, the environment is vulnerable to CVE-2025-23577.

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 (CSRF tokens) on all form submissions and AJAX actions, and ensure all user-supplied data is properly sanitized before output using WordPress sanitization functions like esc_html() and esc_attr().

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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