CVE-2025-31070
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in LambertGroup HTML5 Radio Player - WPBakery Page Builder Addon lbg-cleverbakery allows Path Traversal.This issue affects HTML5 Radio Player - WPBakery Page Builder Addon: from n/a through <= 2.5.
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 · moderate confidenceA path traversal vulnerability in the HTML5 Radio Player plugin for WPBakery allows attackers to access files outside the restricted directory through improper path validation. The vulnerability is exploitable via a web request without authentication, potentially allowing unauthorized file access.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm HTML5 Radio Player plugin is installedLocate the plugin files in the WordPress plugins directory (wp-content/plugins/html5-radio-player or similar naming). If using WordPress admin, check the Plugins page for 'HTML5 Radio Player' in the list of installed plugins.Affected if The plugin appears in the installed plugins list or plugin directory.
-
Identify the installed plugin versionCheck the plugin's main PHP file (usually html5-radio-player.php) for the 'Version' header in the plugin comment block, or look in the plugin's readme.txt file.Affected if The version number cannot be determined or is unknown - treat as potentially affected.
-
Verify the plugin exposes file-serving functionalityExamine the plugin's PHP files for functions that handle file requests (file_get_contents, include, require, readfile, fopen with user input). Look for AJAX handlers or direct file access endpoints.Affected if The plugin contains file-reading code that processes user-supplied paths without proper validation.
-
Test for path traversal vulnerabilityIf file-serving endpoints exist, attempt a controlled test request with a path containing '../' sequences (e.g., ?file=../../wp-config.php). Observe if the response reveals files outside the intended directory.Affected if Requests with '../' sequences successfully return files from directories outside the plugin's intended scope.
-
Check if the vulnerable endpoints are unauthenticatedReview the plugin's access controls on identified file-serving functions. Confirm whether the functions check user authentication or capabilities before processing file requests.Affected if The file-serving functionality processes requests without requiring login or capability checks.
If the HTML5 Radio Player plugin is installed and its file-serving functionality is accessible without authentication, the environment is likely affected by this path traversal vulnerability.
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 dataImplement proper path validation using realpath() and canonicalization to ensure file access is restricted to allowed directories. Sanitize all user-supplied path inputs and reject sequences like '../'
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31070 — 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-31070 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