dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-14353

HIGH · 7.5 CVSS v3.1 Published 2026-03-07
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 ZIP Code Based Content Protection plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 1.0.2 via the 'zipcode' parameter. This is 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 ZIP Code Based Content Protection WordPress plugin versions up to 1.0.2 contains an unauthenticated SQL injection vulnerability in the 'zipcode' parameter. The plugin fails to properly escape user input and does not use prepared SQL statements, allowing attackers to inject arbitrary SQL queries to extract sensitive data from the database.

MitigationUpgrade to the latest version of the plugin that addresses this vulnerability. If no patch is available, remove the plugin or implement web application firewall (WAF) rules to block SQL injection attempts targeting the zipcode parameter.

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. Identify if the ZIP Code Based Content Protection plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'ZIP Code Based Content Protection' or 'zip-code-based-content-protection'. Alternatively, check the /wp-content/plugins/ directory for a folder named 'zip-code-based-content-protection' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the ZIP Code Based Content Protection plugin. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file for a 'Version' header in the plugin comment block.
    Affected if The version is 1.0.2 or lower, or if the version cannot be determined but the plugin is installed
  3. Determine if the vulnerable zipcode parameter is exposed
    Identify the form or endpoint that accepts the 'zipcode' parameter. This is typically a frontend form where users enter a zip code to access protected content. Check if this form is accessible without authentication (not behind a login wall).
    Affected if The zipcode input field is publicly accessible without requiring login or elevated privileges
  4. Verify the SQL injection vulnerability exists
    Test the zipcode parameter with a simple time-based SQL injection payload (e.g., zipcode=12345' AND SLEEP(5)-- -) using a tool like Burp Suite or curl. If the response delays by approximately 5 seconds, the vulnerability is present. Alternatively, observe if the parameter reflects SQL syntax errors in the response.
    Affected if The application responds with delayed execution (time-based) or displays SQL error messages when special characters are submitted in the zipcode parameter

A user is affected if the ZIP Code Based Content Protection plugin version 1.0.2 or lower is installed and the zipcode parameter is accessible to unauthenticated users, as confirmed by successful SQL injection testing.

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

Upgrade to the latest version of the plugin that addresses this vulnerability. If no patch is available, remove the plugin or implement web application firewall (WAF) rules to block SQL injection attempts targeting the zipcode parameter.

Recommended fix Moderate confidence

Check WordPress plugin repository for version >1.0.2

  1. 1. Check the WordPress plugin repository for the ZIP Code Based Content Protection plugin
  2. 2. Verify if a version newer than 1.0.2 is available
  3. 3. If a fixed version is available, update the plugin to that version through the WordPress admin dashboard or via wp-cli: wp plugin update zip-code-based-content-protection
  4. 4. If no fixed version is available, consider disabling and removing the plugin until a patch is released
  5. 5. Audit database logs for any suspicious SQL queries targeting the zipcode parameter
Caveat Unknown - review plugin changelog for any breaking changes between versions

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-14353 — 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-14353 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