CVE-2025-13652
SQL Injection in CBX Bookmark Plugin Allows Data Exposure
Publication date: 2026-01-06
Last updated on: 2026-01-06
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | cbxwpbookmark | to 2.0.4 (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
Can you explain this vulnerability to me?
The CBX Bookmark & Favorite plugin for WordPress has a generic SQL Injection vulnerability via the 'orderby' parameter in all versions up to and including 2.0.4. This happens because the plugin does not properly escape user input and does not sufficiently prepare the SQL query. As a result, authenticated users with Subscriber-level access or higher can inject additional SQL queries into existing ones, potentially extracting sensitive information from the database.
How can this vulnerability impact me? :
This vulnerability can allow an authenticated attacker with Subscriber-level access or above to execute additional SQL queries on the database. This can lead to unauthorized extraction of sensitive information from the database, potentially compromising data confidentiality.
What immediate steps should I take to mitigate this vulnerability?
Update the CBX Bookmark & Favorite WordPress plugin to version 2.0.5 or later, as this update includes extensive modifications likely addressing the SQL Injection vulnerability described in CVE-2025-13652. [2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows authenticated attackers to extract sensitive information from the database via SQL Injection. This exposure of sensitive data could lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access. [2]