LioneWordPress extension · Axiomthemes
CVE-2025-58950
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 axiomthemes Lione lione allows PHP Local File Inclusion.This issue affects Lione: from n/a through <= 1.16.
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 confidenceThe Lione WordPress theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly used in include/require statements without adequate sanitization. An attacker can exploit this to read sensitive files from the local filesystem by manipulating the include path, potentially exposing configuration files, credentials, or executing arbitrary PHP code if the attacker can place malicious files on the server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
LioneWordPress extension
<= 1.16CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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.
-
Confirm Lione theme is installedNavigate to WordPress admin > Appearance > Themes and check if the Lione theme by axiomthemes is active. Note the installed version displayed.Affected if Lione theme version 1.16 or lower is active on the WordPress site
-
Locate dynamic include/require patternsSearch theme PHP files for include, require, include_once, or require_once statements that use variables (such as $_GET, $_POST, or other user-controlled input) as the file path.Affected if Any include/require statement uses unsanitized user input as the path argument
-
Identify the vulnerable parameterExamine the specific include/require code found in step 2. Check if the parameter passed to include/require is derived from request parameters (e.g., $_REQUEST, $_GET, $_POST) without using basename() or whitelist validation.Affected if User-supplied input reaches the include/require without basename() sanitization or whitelist validation
-
Test for LFI exploitation potentialIf vulnerable code is found, attempt to access a known file using the vulnerable parameter (e.g., adding ?param=../../../../wp-config.php to a request). Check if the file contents are returned or displayed.Affected if The parameter allows directory traversal (../ sequences) and returns file contents from outside the intended directory
-
Review access logs for exploitation attemptsExamine web server access logs for unusual requests targeting the Lione theme with traversal sequences in query parameters.Affected if Logs show requests with ../ sequences or attempts to access sensitive files through theme parameters
A user is affected if the Lione theme version 1.16 or lower is installed AND dynamic include/require statements use unsanitized user input that allows directory traversal.
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 dataUpgrade to a patched version of the Lione theme (if available) or implement strict input validation using basename() and whitelist validation on any parameters used in include/require statements. If the vulnerable code is not essential, remove the dynamic include functionality entirely.
Fix this in Lione
Scoped from the published advisory
- 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-58950 — 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-58950 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