Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-7515 – Unauthenticated Local File Inclusion (LFI) leading to RCE – BetterDocs Pro WordPr…

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-7515 is a critical Local File Inclusion (LFI) vulnerability in the BetterDocs Pro WordPress plugin, affecting all versions up to and including 3.8.0. The flaw allows unauthenticated remote attackers to include and execute arbitrary PHP files on the server via the doc_style parameter, with a CVSS v3.1 base score of 9.8 (Critical). In the worst-case scenario — where an attacker can also upload PHP files to the server — this vulnerability results in full unauthenticated Remote Code Execution (RCE).

Technical details

  • Root cause: Improper control of a filename used in a PHP include/require statement (CWE-98); the doc_style parameter is not properly sanitized or validated before being used to resolve a file path, allowing an attacker to supply an arbitrary path.
  • Trigger conditions: The vulnerability is exploitable with no authentication, no user interaction, and under low attack complexity. It requires only network access to a WordPress installation running BetterDocs Pro ≤ 3.8.0.
  • Attack vector: Remote, unauthenticated HTTP request supplying a malicious value to the doc_style parameter, causing the server to include an attacker-controlled PHP file.
  • Impact: Successful exploitation enables execution of arbitrary PHP code in included files, bypassing access controls, exposing sensitive server-side data, and — where an attacker can upload PHP files (e.g., via a separate upload mechanism) — achieving full Remote Code Execution (RCE) on the underlying server. CVSS scores reflect confidentiality, integrity, and availability impact all rated High.

Affected software

  • BetterDocs Pro (WordPress plugin by WPDeveloper) — all versions from the beginning up to and including 3.8.0

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate action: Update BetterDocs Pro to a version above 3.8.0. Consult the vendor’s official changelog at betterdocs.co/changelog to identify and apply the latest available patched release.
  • If immediate patching is not possible: Consider temporarily restricting public access to WordPress documentation pages powered by BetterDocs Pro at the network or web server level, and audit server-writable directories to limit any existing file upload exposure that could be leveraged for RCE escalation.
  • General hardening: Audit WordPress file permissions to prevent unauthorized PHP file uploads, and ensure server-side PHP execution is disabled in upload directories as a compensating control.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge