dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4348

HIGH · 7.5 CVSS v3.1 Published 2026-05-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 BetterDocs Pro plugin for WordPress is vulnerable to SQL Injection via the `get_current_letter_docs` and `docs_sort_by_letter` AJAX actions in all versions up to, and including, 3.7.0. This is due to the `limit` POST parameter being interpolated directly into a SQL query string before being passed to `$wpdb->prepare()`, which only parameterizes other variables. 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. The Encyclopedia feature must be enabled in BetterDocs Pro settings for the vulnerability to be exploitable.

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 BetterDocs Pro plugin for WordPress versions up to 3.7.0 contains a SQL Injection vulnerability in the `get_current_letter_docs` and `docs_sort_by_letter` AJAX action handlers. The vulnerability stems from the `limit` POST parameter being directly concatenated into the SQL query string before being passed to `$wpdb->prepare()`, which only parameterizes other variables in the query. This allows unauthenticated attackers to inject arbitrary SQL queries. The Encyclopedia feature must be enabled for exploitation.

MitigationUpdate BetterDocs Pro to version greater than 3.7.0 when available. Until patched, disable the Encyclopedia feature in plugin settings and consider restricting AJAX endpoints at the web server level.

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 BetterDocs Pro installation
    In WordPress admin, go to Plugins > Installed Plugins and locate BetterDocs Pro. Note the installed version number displayed.
    Affected if The plugin is installed and the version is 3.7.0 or lower
  2. Confirm Encyclopedia feature is enabled
    Navigate to BetterDocs Pro settings (typically under BetterDocs > Settings or Encyclopedia > Settings in the WordPress admin). Look for an option related to Encyclopedia and verify whether it is turned on or enabled.
    Affected if The Encyclopedia feature is enabled in the plugin settings
  3. Check AJAX endpoint accessibility
    Verify that the AJAX action handlers are accessible. The vulnerable endpoints are typically at /wp-admin/admin-ajax.php with action parameters 'get_current_letter_docs' or 'docs_sort_by_letter'. Attempt a request to one of these endpoints with a test 'limit' parameter to confirm it processes the request.
    Affected if The AJAX endpoints respond and process the 'limit' parameter without additional authentication checks (unauthenticated access)
  4. Review SQL query construction in plugin code
    If file access is available, examine the plugin source code for the functions handling 'get_current_letter_docs' and 'docs_sort_by_letter' AJAX actions. Look for direct concatenation of the 'limit' POST parameter into SQL queries before the $wpdb->prepare() call.
    Affected if The code shows direct string concatenation of the 'limit' parameter into SQL without proper sanitization

You are affected if BetterDocs Pro version 3.7.0 or lower is installed, the Encyclopedia feature is enabled, and the AJAX endpoints are 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BetterDocs Pro to version greater than 3.7.0 when available. Until patched, disable the Encyclopedia feature in plugin settings and consider restricting AJAX endpoints at the web server level.

Recommended fix Moderate confidence

Version 3.7.1 or later (any version higher than 3.7.0)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate BetterDocs Pro in the plugin list
  4. 4. Check if an update is available (compare current version to the latest available version)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. After updating, verify that the Encyclopedia feature settings are still configured as needed
  7. 7. Test the affected AJAX endpoints (get_current_letter_docs and docs_sort_by_letter) to confirm functionality works correctly after the patch

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
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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