LunnaWordPress extension · Axiomthemes
CVE-2025-58935
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 Lunna lunna allows PHP Local File Inclusion.This issue affects Lunna: from n/a through <= 1.15.
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 Lunna WordPress theme by axiomthemes contains a Local File Inclusion (LFI) vulnerability (CVSS 9.8 critical) in its PHP include/require statements. Attackers can exploit improper control of filenames to read sensitive server files via path traversal, potentially exposing configuration files, credentials, or achieving code execution.
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
LunnaWordPress extension
<= 1.15CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Identify Lunna theme versionIn WordPress admin, go to Appearance > Themes to view the installed theme version. Alternatively, check the style.css file in wp-content/themes/lunna/ for the 'Version:' header, or use WP-CLI: wp theme get lunna --field=versionAffected if Version is 1.15 or lower
-
Verify theme is activeConfirm whether the Lunna theme is currently activated on the WordPress site. Check via WordPress admin under Appearance > Themes or with WP-CLI: wp theme list --status=activeAffected if Lunna theme is the active theme
-
Locate file inclusion codeSearch the theme files for include/require statements using dynamic parameters (e.g., grep -r 'include.*\$_' or 'require.*\$_' in the wp-content/themes/lunna/ directory). Focus on PHP files in the include/ folder mentioned in the CVE descriptionAffected if Dynamic file inclusion using user-controlled input exists in the theme
-
Inspect vulnerable parametersReview the identified include/require statements for parameters that accept file paths without sanitization. Common patterns include ?file=, ?page=, ?template=, or ?path= in URL parametersAffected if File inclusion parameters accept unsanitized input and can traverse directories (e.g., ../../)
User is affected if Lunna theme version 1.15 or lower is installed and active, with the vulnerable file inclusion code present and accessible.
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 Lunna theme; if unavailable, disable the theme immediately and replace with a secured alternative, or deploy WAF rules to block path traversal patterns in requests.
Fix this in Lunna
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58935 — 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-58935 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