dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30524

CRITICAL · 9.3 CVSS v3.1 Published 2025-03-26
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 origincode Product Catalog displayproduct allows SQL Injection.This issue affects Product Catalog: from n/a through <= 1.0.4.

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 displayproduct component of the origincode Product Catalog WordPress plugin allows attackers to inject malicious SQL commands via unsanitized input. The vulnerability affects versions up to and including 1.0.4, enabling remote attackers to potentially exfiltrate data, modify database content, or compromise the underlying application.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation and sanitization on all user-supplied parameters in the displayproduct functionality. Update to a patched version if 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
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. Locate the Product Catalog plugin installation
    Check the wp-content/plugins/ directory for a folder named 'product-catalog', 'origincode-product-catalog', or similar naming pattern for the origincode Product Catalog plugin
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    Open the main plugin PHP file (typically in the plugin root folder) and read the Version header from the plugin comment block, or check the readme.txt file for the 'Stable tag' or 'Version' field
    Affected if The installed version is 1.0.4 or any lower version up to and including 1.0.4
  3. Confirm the displayproduct component is present
    Search within the plugin folder for files or functions named 'displayproduct' - this may appear as a shortcode, function, or template file handling the product display functionality
    Affected if The displayproduct component exists and is accessible within the plugin code
  4. Check for unauthenticated access to displayproduct
    Determine if the displayproduct functionality can be accessed without authentication - test accessing any shortcode or endpoint associated with displayproduct as an unauthenticated visitor
    Affected if The displayproduct functionality is reachable without login and processes user-supplied parameters

A user is affected if the origincode Product Catalog plugin is installed at version 1.0.4 or lower and the displayproduct component is accessible, as the SQL injection flaw exists in that component via unsanitized input parameters.

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

Replace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation and sanitization on all user-supplied parameters in the displayproduct functionality. Update to a patched version if available.

Recommended fix Moderate confidence

Latest version of origincode Product Catalog (version > 1.0.4)

  1. Obtain the latest version of the origincode Product Catalog plugin from the official WordPress repository or vendor
  2. Backup your WordPress database and files before updating
  3. Deactivate the current Product Catalog plugin
  4. Delete the existing Product Catalog plugin files
  5. Install the latest version of the Product Catalog plugin
  6. Activate the new version
  7. Verify the SQL injection vulnerability is resolved by testing the displayproduct functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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