dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-9321

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-23
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 Zero-click

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
The WPCasa plugin for WordPress is vulnerable to Code Injection in all versions up to, and including, 1.4.1. This is due to insufficient input validation and restriction on the 'api_requests' function. This makes it possible for unauthenticated attackers to call arbitrary functions and execute code.

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

The WPCasa WordPress plugin contains a code injection vulnerability in the 'api_requests' function in versions up to 1.4.1. The function lacks proper input validation and access controls, allowing unauthenticated attackers to invoke arbitrary PHP functions and achieve remote code execution.

MitigationUpdate the WPCasa plugin to a version beyond 1.4.1 once a patch is released. As an interim measure, disable the plugin or restrict access to the api_requests endpoint via web server configuration until a fix is 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Verify WPCasa plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the wpcasa folder, or list installed plugins via wp-cli: wp plugin list --name=wpcasa
    Affected if The wpcasa folder exists in the plugins directory
  2. Determine installed WPCasa version
    Open the main plugin file (usually wpcasa.php) and check the Version header in the plugin comment block, or run: wp plugin get wpcasa --format=json
    Affected if The version is 1.4.1 or earlier (versions up to and including 1.4.1 are vulnerable)
  3. Confirm the vulnerable api_requests function exists
    Search the plugin files for the string 'function api_requests' to verify the vulnerable function is present in the installed version
    Affected if The function 'api_requests' is found in the plugin code
  4. Check if the plugin API endpoint is accessible
    Test access to the WordPress AJAX endpoint (wp-admin/admin-ajax.php) with a crafted request targeting the wpcasa api_requests action, or inspect the plugin to confirm the function is hooked to a public action
    Affected if The wpcasa_api_requests action is hooked to a publicly accessible hook (such as wp_ajax_nopriv_ or wp_ajax_)
  5. Review access logs for suspicious requests
    Examine web server access logs (Apache/nginx) for requests to admin-ajax.php containing wpcasa-related actions or unusual parameter patterns
    Affected if Requests contain wpcasa actions with unexpected or malicious parameter values

A user is affected if the WPCasa plugin versions 1.4.1 or earlier are installed and the api_requests function is accessible to unauthenticated users.

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

Update the WPCasa plugin to a version beyond 1.4.1 once a patch is released. As an interim measure, disable the plugin or restrict access to the api_requests endpoint via web server configuration until a fix is available.

Recommended fix Moderate confidence

Any version of WPCasa newer than 1.4.1

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the WPCasa plugin
  4. Check the current version installed (should be 1.4.1 or below)
  5. Click 'Update Now' to update WPCasa to the latest available version
  6. Verify the update was successful and the plugin is now running a version newer than 1.4.1

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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