CVE-2025-68885
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 page-carbajal Custom Post Status custom-post-status allows Stored XSS.This issue affects Custom Post Status: from n/a through <= 1.1.0.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the Custom Post Status WordPress plugin allows authenticated administrators to be tricked into submitting malicious requests that inject Stored XSS payloads into plugin settings. When other users view the affected admin pages, the injected JavaScript executes in their browsers.
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.
-
Confirm Custom Post Status plugin is installedGo to WordPress Admin > Plugins and verify the Custom Post Status plugin is active. Note the installed version number from the plugin list.Affected if The plugin is installed and active with no version listed in the CVE as patched
-
Inspect plugin settings for XSS payloadsNavigate to the Custom Post Status plugin settings pages. View the page source or inspect form fields for any suspicious script tags, javascript: URLs, or event handlers (onclick, onerror, onload) in setting values.Affected if Plugin settings contain unsanitized script tags or event handlers that could execute when other admins view the page
-
Review custom post statuses for stored XSSVisit the post status management section in the plugin (usually under Posts or Settings). Check if any custom post status names, descriptions, or labels contain JavaScript code or HTML that could execute in a browser.Affected if Custom post status names or descriptions contain executable JavaScript or unsanitized HTML
-
Verify CSRF protection exists in plugin formsView the HTML source of plugin settings forms. Verify that each form includes a nonce field (typically named wpnonce, _wpnonce, or similar) and uses POST method, not GET.Affected if Plugin forms lack nonce verification or use GET requests for state-changing actions
If the plugin is active and either its settings/statuses contain XSS payloads or its forms lack CSRF nonces, the environment is vulnerable to CVE-2025-68885.
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 dataUpdate the plugin to a patched version if available. Until then, disable the plugin or implement strict CSRF protection (nonces) on all plugin forms and verify proper output sanitization.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68885 — 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-68885 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