VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 1 known issue Latest disclosed May 06, 2026

BetterDocs Pro Vulnerabilities

Review known vulnerability records for the WordPress plugin BetterDocs Pro (`betterdocs-pro`), including severity, CVE references, affected versions, and patch status.

Recent tracked CVEs on this page include CVE-2026-4348, so operators can jump from disclosure to patch validation without scanning the full feed first.

View on WordPress.org Back to Feed
Known Records
1
High or Critical
1
Patch Coverage
100%
Last Updated
May 06, 2026
Related Security Guides

Use these guides while reviewing BetterDocs Pro fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize BetterDocs Pro remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is betterdocs-pro before acting on any CVE from this cluster.
2. Sort by Severity
Start with 1 high or critical record, then review medium and unrated findings with public references.
3. Check Patch Evidence
1 record include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2026-4348 High
SQL Injection remediation for BetterDocs Pro

Affected range: Versions up to 3.7.0. Fixed version: 3.7.1.

Priority CVE Quick Links

Fast paths into BetterDocs Pro CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
1
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2026-4348
BetterDocs Pro <= 3.7.0 - Unauthenticated SQL Injection via Encyclopedia 'limit' Par...
 SQL Injection Versions up to 3.7.0 3.7.1 CVSS 7.5
CVE-2026-4348 High 3.7.1
CVE-2026-4348 BetterDocs Pro SQL Injection

BetterDocs Pro <= 3.7.0 - Unauthenticated SQL Injection via Encyclopedia 'limit' Parameter

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for BetterDocs Pro so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
1 record include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 1 high severity finding.
Recent CVEs
CVE-2026-4348
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for BetterDocs Pro

Sorted by latest disclosure date so newly published issues surface first.

Plugin High Patched: Yes CVE-2026-4348
CVE-2026-4348: BetterDocs Pro <= 3.7.0 - Unauthenticated SQL Injection via Encyclopedia 'limit' Parameter

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 stri...

Published
May 06, 2026
Patched Release
3.7.1
Affected Versions
Versions up to 3.7.0
Next Step
Update to 3.7.1 or newer if supported.
Review CVE-2026-4348 fixed version details Open CVE Reference