dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-9073

HIGH · 7.5 CVSS v3.1 Published 2025-09-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 All in one Minifier plugin for WordPress is vulnerable to SQL Injection via the 'post_id' parameter in all versions up to, and including, 3.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 All in one Minifier WordPress plugin up to version 3.2 contains a SQL Injection vulnerability in the 'post_id' parameter. Unauthenticated attackers can exploit insufficient input escaping and lack of prepared SQL statements to inject arbitrary SQL queries, potentially extracting sensitive data from the database.

MitigationUpdate the All in one Minifier plugin to the latest version immediately. If no patched version exists, consider disabling the plugin until a fix is available or implement a web application firewall (WAF) rule to block malicious 'post_id' parameter values.

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
None
Availability
None

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

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

  1. Confirm plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'All in one Minifier'. Note the version number displayed. Alternatively, check the plugin's main PHP file header for the Version field.
    Affected if The installed version is 3.2 or lower, since the vulnerability affects versions up to 3.2.
  2. Verify the plugin is active
    In WordPress admin, check the Plugins page to confirm whether the All in one Minifier plugin is currently activated.
    Affected if The plugin is active and the version is 3.2 or lower.
  3. Identify accessible endpoints using post_id
    Review your web server logs or use a directory scanning tool to find URLs in your WordPress installation that accept a 'post_id' parameter (commonly found in AJAX handlers or frontend processing files). Common paths include /wp-admin/admin-ajax.php or plugin-specific AJAX endpoints.
    Affected if An endpoint accepting the 'post_id' parameter is publicly accessible (no authentication required) and the plugin is loaded on that request.
  4. Test for SQL injection susceptibility
    Send a crafted request to a post_id endpoint with a test payload such as 'post_id=1 AND 1=1' or 'post_id=1' (single quote). Compare responses - if the application returns different errors or behaves differently, the parameter may be vulnerable.
    Affected if The application reflects SQL syntax errors in its response or returns unexpected data based on boolean-based injection payloads, indicating unsanitized input handling.

You are affected if the All in one Minifier plugin is installed, active, version 3.2 or lower, and exposes an endpoint that processes the 'post_id' parameter without proper SQL prepared statements.

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 All in one Minifier plugin to the latest version immediately. If no patched version exists, consider disabling the plugin until a fix is available or implement a web application firewall (WAF) rule to block malicious 'post_id' parameter values.

Recommended fix Moderate confidence

Latest version available on WordPress plugin repository (version higher than 3.2)

  1. Check the WordPress plugin repository (plugins.trac.wordpress.org) or WordPress admin panel for the All in one Minifier plugin to identify the current installed version
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate the All in one Minifier plugin
  4. If the installed version is 3.2 or below, update the plugin to the latest available version from the WordPress plugin repository
  5. After updating, verify the plugin is functioning correctly on the site

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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