dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30622

CRITICAL · 9.3 CVSS v3.1 Published 2025-04-01
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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in torsteino PostMash postmash-custom allows SQL Injection.This issue affects PostMash: from n/a through <= 1.0.3.

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

SQL injection vulnerability in the PostMash WordPress plugin (postmash-custom component) allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability affects all versions up to and including 1.0.3, with a critical CVSS score of 9.3 indicating potential for complete database compromise.

MitigationUpgrade PostMash to the latest version which implements parameterized queries or prepared statements for all database interactions. If no patch is available, audit the source code and replace all dynamic SQL queries with prepared statements, then validate all user inputs before database operations.

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
Changed
Confidentiality
High
Integrity
None
Availability
Low

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

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

  1. Check if PostMash plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'PostMash' in the list
    Affected if PostMash plugin appears in the installed plugins list
  2. Verify the installed PostMash version
    In the Plugins list, find PostMash and view the version number displayed below the plugin name. Alternatively, check the plugin's main PHP file (usually postmash.php) for the 'Version' header in the plugin comment block
    Affected if The installed version is 1.0.3 or any earlier version (all versions up to 1.0.3 are affected)
  3. Confirm postmash-custom component is active
    Check WordPress for any custom post types, shortcodes, or widgets named 'postmash-custom'. Also check the plugin directory for a file named postmash-custom.php or similar
    Affected if The postmash-custom component is present and enabled on the site
  4. Inspect the plugin source code for unsanitized SQL queries
    Open the main plugin PHP file and search for direct SQL queries using $wpdb->prepare, $wpdb->query, or $wpdb->get_results without proper prepare() calls. Specifically examine any code handling user input (GET/POST parameters) passed directly to SQL statements
    Affected if User-supplied input is directly concatenated into SQL queries without sanitization or prepared statements

The environment is affected if PostMash plugin version 1.0.3 or earlier is installed with the postmash-custom component active and the code contains unsanitized SQL queries handling user input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade PostMash to the latest version which implements parameterized queries or prepared statements for all database interactions. If no patch is available, audit the source code and replace all dynamic SQL queries with prepared statements, then validate all user inputs before database operations.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

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