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

CVE-2025-22557

HIGH · 7.1 CVSS v3.1 Published 2025-01-07
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 cdowp News Publisher Autopilot wpm-news-api allows Cross Site Request Forgery.This issue affects News Publisher Autopilot: from n/a through <= 2.1.4.

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 the cdowp News Publisher Autopilot WordPress plugin (wpm-news-api) allows attackers to execute unauthorized actions on behalf of authenticated administrators. The plugin lacks proper anti-CSRF token validation on state-changing operations, enabling malicious requests to be forged by attackers.

MitigationApply vendor-supplied patch or update to a version beyond 2.1.4; alternatively, implement anti-CSRF tokens (nonces) on all form submissions and AJAX actions within the plugin and validate these tokens server-side before processing 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 checks

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

  1. Verify plugin installation
    Log into WordPress admin and navigate to Plugins > Installed Plugins. Search for 'cdowp News Publisher Autopilot' or 'wpm-news-api' and confirm the plugin is present and active.
    Affected if The plugin is installed and activated on the WordPress site.
  2. Check installed version
    In WordPress admin, go to Plugins > Installed Plugins. Find the cdowp News Publisher Autopilot plugin and note the version number displayed.
    Affected if The installed version is 2.1.4 or lower (the vulnerability exists in versions up to and including 2.1.4).
  3. Inspect plugin for state-changing functions
    Access the site via FTP or file manager. Locate the plugin directory (wp-content/plugins/wpm-news-api or similar). Search PHP files for form submissions and AJAX handlers that perform state-changing operations (e.g., saving settings, creating/updating posts, modifying options).
    Affected if The plugin contains state-changing operations (forms, AJAX actions) that handle data submission.
  4. Verify nonce/CSRF token implementation
    Open the PHP files identified in the previous step. Look for the presence of WordPress nonce verification functions such as wp_verify_nonce(), check_ajax_referer(), or wp_create_nonce() within the state-changing handlers.
    Affected if No nonce verification is found in the state-changing operations, meaning CSRF protection is missing.
  5. Check admin action hooks for CSRF validation
    Examine the plugin's admin action hooks (admin_post_, wp_ajax_) in the main plugin file. Verify whether these hooks include nonce validation before processing any submitted data.
    Affected if Admin action hooks lack nonce validation, allowing forged requests to be processed.

A user is affected if the cdowp News Publisher Autopilot plugin is installed and activated with version 2.1.4 or lower, and the plugin's state-changing operations lack anti-CSRF token 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

Apply vendor-supplied patch or update to a version beyond 2.1.4; alternatively, implement anti-CSRF tokens (nonces) on all form submissions and AJAX actions within the plugin and validate these tokens server-side before processing requests.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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