dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-5100

HIGH · 7.5 CVSS v3.1 Published 2026-05-05
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 AWP Classifieds plugin for WordPress is vulnerable to SQL Injection via the 'regions' parameter array keys in versions up to, and including, 4.4.5 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 AWP Classifieds WordPress plugin versions up to 4.4.5 contains an unauthenticated SQL injection vulnerability in the 'regions' parameter. Attackers can inject malicious SQL via array keys in this parameter due to insufficient input escaping and lack of prepared statements in the underlying SQL query, allowing database data extraction.

MitigationUpgrade the AWP Classifieds plugin to version 4.4.6 or later which contains the patched code, or implement proper input sanitization and prepared statements for the 'regions' 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. Verify AWP Classifieds plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'AWP Classifieds', or inspect the plugin main file header for the Version field, or check /wp-content/plugins/awp-classifieds/awp_classifieds.php
    Affected if The plugin is installed and the version listed is 4.4.5 or lower
  2. Confirm the 'regions' feature is accessible
    The vulnerability affects the 'regions' parameter in the plugin's frontend or API endpoints. Verify if the plugin exposes any public-facing classifieds listings or region-based filtering functionality that uses the 'regions' parameter
    Affected if The plugin's region-based classification feature is enabled or exposed on the site
  3. Check for indicators of SQL injection attempts
    Review web server access logs and WordPress security plugin logs (if installed) for unusual SQL syntax or suspicious patterns in requests containing 'regions' parameter values, such as quotes, UNION statements, or boolean-based injection payloads
    Affected if Suspicious SQL injection patterns are found in logs targeting the 'regions' parameter

A site is affected if it has AWP Classifieds plugin version 4.4.5 or earlier installed with the regions feature 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.

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

Upgrade the AWP Classifieds plugin to version 4.4.6 or later which contains the patched code, or implement proper input sanitization and prepared statements for the 'regions' parameter.

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-2026-5100 — 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-2026-5100 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