CVE-2025-9617
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 · uneditedThe Publish approval plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1. This is due to missing or incorrect nonce validation on the publish_save_option function. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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 confidenceThe Publish approval plugin for WordPress lacks proper nonce validation in its publish_save_option function, allowing unauthenticated attackers to forge administrative requests that modify plugin settings. This CSRF vulnerability requires social engineering to trick a logged-in administrator into clicking a malicious link.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 Publish approval plugin is installedNavigate to WordPress Admin > Plugins and look for 'Publish approval' in the installed plugins listAffected if The plugin appears in the installed plugins list and is activated
-
Check plugin versionClick on the plugin in the plugin list to view its version number, or check the plugin header in /wp-content/plugins/publish-approval/ directoryAffected if The installed version matches or precedes any vulnerable version of the plugin (no patched version specified; treat any version as potentially affected if the nonce validation is missing)
-
Inspect the publish_save_option functionAccess the plugin directory via FTP or file manager, locate the main plugin PHP file, and search for the function 'publish_save_option' to verify it existsAffected if The function exists in the plugin code and lacks a nonce validation check (look for missing wp_verify_nonce or check_admin_referer calls)
-
Review plugin settings accessibilityAttempt to access the plugin settings page while not logged in, or inspect the form submission code for CSRF protection tokensAffected if The settings form submits without requiring a valid nonce token or referer check
A user is affected if the Publish approval plugin is installed and activated, and the settings can be modified through forged requests lacking proper nonce validation.
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.
dbcve · scopedUpdate to a patched version of the plugin once available. Until then, administrators should avoid clicking untrusted links while logged into WordPress admin areas.
Version 1.2 or later
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'Publish approval' plugin
- Check the current installed version (should be 1.1 or earlier)
- Update the plugin to the latest available version (1.2 or higher)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9617 — 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-9617 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