CVE-2026-5100
SQL Injection in AWP Classifieds WordPress Plugin
Publication date: 2026-05-05
Last updated on: 2026-05-05
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| awp_classifieds | plugin | to 4.4.5 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows unauthenticated attackers to perform SQL Injection attacks that can extract sensitive information from the database.
Such unauthorized access to sensitive data could potentially lead to non-compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access.
Can you explain this vulnerability to me?
The AWP Classifieds plugin for WordPress has a vulnerability in versions up to and including 4.4.5 where the 'regions' parameter array keys are not properly escaped or prepared in SQL queries.
This insufficient escaping allows unauthenticated attackers to inject additional SQL queries into existing ones, leading to a SQL Injection vulnerability.
As a result, attackers can manipulate the database queries to extract sensitive information.
How can this vulnerability impact me? :
This vulnerability can allow unauthenticated attackers to extract sensitive information from your website's database by injecting malicious SQL code.
Because the attacker does not need to be authenticated, the risk of data exposure is higher.
The impact is primarily on confidentiality, as indicated by the CVSS score which rates the confidentiality impact as high.