CVE-2025-32159
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme Radius Blocks radius-blocks allows PHP Local File Inclusion.This issue affects Radius Blocks: from n/a through <= 2.2.1.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability in the RadiusTheme Radius Blocks WordPress plugin (versions up to 2.2.1) allows attackers to include arbitrary PHP files from the server due to improper control of filename parameters in include/require statements. This can lead to remote code execution if attackers can control the included files.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Radius Blocks plugin is installedAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'Radius Blocks' by RadiusTheme. Alternatively, check the /wp-content/plugins/ directory for the radius-blocks folder.Affected if The plugin is present in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, click on the plugin to view its details and version number. Or inspect the main plugin file (e.g., radius-blocks.php) and look for the 'Version' header comment.Affected if The installed version is 2.2.1 or any version up to and including 2.2.1
-
Identify file inclusion code pathsExamine the plugin source code for dynamic include(), require(), include_once(), or require_once() statements that use variables or request parameters as file paths. Search for patterns like 'include($_REQUEST' or 'require($' within the plugin directory.Affected if The plugin contains file inclusion logic that uses unsanitized input from user requests (GET/POST parameters)
-
Check for accessible vulnerable endpointsReview the plugin for AJAX handlers or front-end shortcodes that might process file inclusion parameters. Test if the plugin exposes any URL parameters that could be manipulated to trigger file inclusion (e.g., ?file=../../).Affected if The plugin exposes an endpoint or parameter that allows controlling the file path in include/require statements
-
Review server access logs for exploitation attemptsSearch web server access logs (Apache error.log, Nginx access.log) for unusual requests to the plugin directory containing path traversal patterns (e.g., ../, ..\) or attempts to include PHP files from common paths like /etc/passwd or wp-config.php.Affected if Logs show requests with path traversal sequences targeting the Radius Blocks plugin
A user is affected if the Radius Blocks plugin version is 2.2.1 or lower AND the plugin processes file paths from user input without proper sanitization.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the radius-blocks plugin to the latest patched version. If no patch is available, disable or remove the plugin until a fix is released. Review and sanitize all file inclusion operations in the plugin code.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32159 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32159 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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