dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-13652

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 CBX Bookmark & Favorite plugin for WordPress is vulnerable to generic SQL Injection via the ‘orderby’ parameter in all versions up to, and including, 2.0.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 CBX Bookmark & Favorite WordPress plugin versions up to 2.0.4 contains a SQL injection vulnerability in the 'orderby' parameter. The parameter is not properly escaped before being used in a SQL query, and the query lacks sufficient preparation with parameterized statements. An authenticated attacker with Subscriber-level access can inject arbitrary SQL commands to exfiltrate sensitive data from the database.

MitigationUpgrade the CBX Bookmark & Favorite plugin to version 2.0.5 or later, which contains the security fix. Until an update is available, consider restricting user registration or disabling the plugin if subscriber-level access is not needed.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Check if CBX Bookmark & Favorite plugin is installed
    In WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'CBX Bookmark & Favorite' or check the plugin files in wp-content/plugins/ directory for the folder named 'cbxbookmark'
    Affected if Plugin is installed and active
  2. Determine installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find CBX Bookmark & Favorite, and note the version number displayed. Alternatively, check the main plugin file (e.g., cbxbookmark.php) for the 'Version' header in the plugin comment block
    Affected if Version is 2.0.4 or lower (any version up to and including 2.0.4)
  3. Verify subscriber-level access exists
    Check WordPress user roles at Users > All Users to see if any users have the Subscriber role, or check if user registration is enabled at Settings > General > Membership
    Affected if Subscriber-level accounts exist or user registration allows subscriber-level access
  4. Confirm plugin features are accessible to subscribers
    Test accessing the bookmark functionality as a subscriber-level user, or review the plugin's shortcode or widget settings to determine if 'orderby' parameter is used in any public-facing queries
    Affected if Subscribers can trigger the orderby parameter in plugin queries (e.g., via shortcode with orderby attribute)

User is affected if the CBX Bookmark & Favorite plugin version is 2.0.4 or lower and subscriber-level users exist or can register, enabling them to exploit the unescaped orderby parameter in SQL queries.

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 the CBX Bookmark & Favorite plugin to version 2.0.5 or later, which contains the security fix. Until an update is available, consider restricting user registration or disabling the plugin if subscriber-level access is not needed.

Recommended fix Moderate confidence

CBX Bookmark & Favorite version 2.0.5 or later

  1. Update the CBX Bookmark & Favorite plugin to version 2.0.5 or later
  2. After updating, verify that the plugin functions correctly on the WordPress site
  3. Ensure that user roles are properly configured - subscribers should only have appropriate access levels

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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