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

CVE-2025-58255

CRITICAL · 9.6 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 yonisink Custom Post Type Images custom-post-types-image allows Code Injection.This issue affects Custom Post Type Images: from n/a through <= 0.5.

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

A Cross-Site Request Forgery (CSRF) vulnerability in the yonisink Custom Post Type Images WordPress plugin (versions <= 0.5) allows attackers to forge requests that result in code injection. The lack of proper CSRF token validation on sensitive actions enables malicious actors to trick authenticated administrators into executing unintended code through crafted form submissions.

MitigationImplement nonces/tokens for all state-changing actions in the plugin and apply proper input sanitization and output escaping to prevent code injection. Update to a patched version when available.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checks

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

  1. Verify Custom Post Type Images plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and search for 'Custom Post Type Images' or check the /wp-content/plugins/ directory for the plugin folder
    Affected if plugin is present in the plugins directory or listed in WordPress admin
  2. Identify installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins > Custom Post Type Images and note the version number displayed; alternatively, read the main plugin PHP file header for 'Version:' field
    Affected if version number cannot be determined or is within an affected range (contact vendor for specific vulnerable versions)
  3. Inspect admin action handlers for nonce verification
    Examine PHP files in the plugin directory for form processing and AJAX handlers; search for 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' functions; check if nonce fields are present in HTML forms
    Affected if state-changing functions (save, update, delete, upload operations) lack nonce verification calls or nonce field generation
  4. Test for CSRF vulnerability
    Create a malicious HTML page with a form targeting the plugin admin action URLs (found in plugin source); attempt to submit the form without a valid nonce token while authenticated as administrator
    Affected if the action executes successfully without returning a nonce verification error
  5. Check for admin referer verification
    Review PHP code for 'check_admin_referer' or 'wp_verify_nonce' calls immediately before any database write, file upload, or settings change operations
    Affected if critical state-changing operations proceed without verifying the request referer or nonce

Environment is affected if the Custom Post Type Images plugin is installed and its code lacks proper nonce validation on state-changing operations, allowing authenticated administrators to be exploited via CSRF attacks.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement nonces/tokens for all state-changing actions in the plugin and apply proper input sanitization and output escaping to prevent code injection. Update to a patched version when available.

Recommended fix Moderate confidence

Latest version available in the WordPress Plugin Directory (ensure version is greater than 0.5)

  1. Log in to the WordPress admin dashboard.
  2. Navigate to 'Plugins' > 'Installed Plugins'.
  3. Locate the 'Custom Post Type Images' plugin by yonisink.
  4. Click 'Update Now' to upgrade to the latest version available in the WordPress Plugin Directory.
  5. If automatic updates are disabled, download the latest version from wordpress.org and upload it via 'Add New' > 'Upload Plugin'.
  6. After updating, test the plugin functionality to ensure the site operates normally.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

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