Vulnerability in Prevent Direct Access – Protect WordPress Files (WordPress plugin) (CVE-2026-3835)
Summary
Vulnerability in Prevent Direct Access – Protect WordPress Files (WordPress plugin) (CVE-2026-3835). Risk of unauthorized operations or information disclosure. Exploitable via LIKE.
Original description
The description as published by the source.
The Prevent Direct Access – Protect WordPress Files plugin for WordPress is vulnerable to unauthorized access of protected files due to insufficient token validation in the get_advance_file_by_url() method in all versions up to, and including, 2.8.8.8 The method uses a SQL LIKE operator for token lookup without escaping wildcard characters via $wpdb->esc_like(). This makes it possible for unauthenticated attackers to bypass the private token requirement by supplying SQL wildcard characters (such as %) as the token value, matching any record in the plugin's file table and downloading any protected file.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3835 has been found in Prevent Direct Access – Protect WordPress Files (WordPress plugin).
Attackers can target a specific entry point like LIKE over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Prevent Direct Access – Protect WordPress Files (WordPress plugin) CVE-2026-3835" on the vendor's site.
CVE-2026-3835 (Prevent Direct Access – Protect WordPress Files (WordPress plugin)) — CWE-285 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: LIKE
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in Prevent Direct Access – Protect WordPress Files (WordPress plugin). Attackers reach the vulnerable code path via LIKE without authentication.
Check the vendor advisory for the affected versions of Prevent Direct Access – Protect WordPress Files (WordPress plugin). Attack surface: LIKE.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Prevent Direct Access – Protect WordPress Files (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web wordpress.org
- web security@wordfence.com
- web github.com
- web security@wordfence.com