CVE-2025-60208
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 Tusko Trush Advanced Custom Fields : CPT Options Pages acf-cpt-options-pages allows Object Injection.This issue affects Advanced Custom Fields : CPT Options Pages: from n/a through <= 2.0.9.
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 confidenceCSRF vulnerability in the acf-cpt-options-pages plugin allows authenticated attackers to trick administrators into performing unwanted actions via malicious requests, leading to PHP Object Injection that could result in arbitrary code execution.
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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 acf-cpt-options-pages plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'ACF CPT Options Pages' or check the plugins directory at /wp-content/plugins/ for a folder named 'acf-cpt-options-pages'Affected if Plugin is present in the WordPress installation
-
Identify installed plugin versionCheck the plugin header in acf-cpt-options-pages.php or the WordPress plugins admin page for the version numberAffected if Version is unpatched or unknown (no patch version specified in advisory)
-
Check if plugin settings expose options pagesNavigate to the plugin settings or ACF options pages in WordPress admin - look for any custom post type options pages created by the plugin at /wp-admin/admin.php?page=*Affected if Custom options pages are accessible and functional in the admin dashboard
-
Verify admin authentication is possibleConfirm WordPress administrator account exists and can access the admin dashboard where the plugin functionality is exposedAffected if Administrator-level user accounts exist and can log in to trigger the CSRF vector
-
Inspect plugin source for deserialization functionsExamine plugin PHP files for use of unserialize() on user-controlled input, particularly in AJAX handlers or form processing files within the plugin directoryAffected if Plugin code contains unserialize() calls processing external or form-submitted data without proper sanitization
User is affected if the acf-cpt-options-pages plugin is installed and any administrator can be tricked into submitting a crafted request that triggers unsafe deserialization.
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 to latest plugin version when available; implement CSRF nonces/tokens on all form submissions and AJAX endpoints; validate and sanitize all user inputs to prevent object injection.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60208 — 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-60208 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