CVE-2025-49360
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 AncoraThemes Militarology militarology allows PHP Local File Inclusion.This issue affects Militarology: from n/a through <= 1.0.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 Militarology theme by AncoraThemes contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filename parameters in include/require statements. This allows attackers to read sensitive local files on the server by manipulating file path parameters, potentially exposing configuration files, credentials, or enabling code execution.
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
- 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.
-
Identify if Militarology theme is installedCheck your WordPress themes directory (wp-content/themes/) for a folder named militarology, or view the currently active theme in WordPress admin under Appearance > ThemesAffected if The militarology theme folder exists in your themes directory and is the active theme
-
Determine the installed theme versionLocate the style.css file within the militarology theme folder and read the Version field in the file header comment, or view the theme version in WordPress admin theme detailsAffected if The version is older than the patched version or cannot be verified as patched
-
Inspect for vulnerable file inclusion patternsSearch theme PHP files for include, require, include_once, or require_once statements that use variable parameters without validation, for example: include($_GET['parameter']) or require($var)Affected if Unvalidated file inclusion code that uses user-supplied input in the file path is found in theme PHP files
-
Check for accessible vulnerable parametersTest if URL parameters controlling file paths are reachable by requesting theme pages with query parameters like ?file=something or ?template=somethingAffected if The application accepts file path parameters without validation and returns file contents
-
Review access logs for exploitation attemptsExamine web server access logs for requests containing ../ (directory traversal patterns) targeting theme files or suspicious path parametersAffected if Evidence of directory traversal attempts or LFI exploitation is found in server logs
You are affected if the Militarology theme is installed and active, running an unpatched version with unvalidated file inclusion code that accepts user-controlled path parameters.
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 Militarology theme to the latest patched version. If no patch is available, disable the theme immediately and implement WAF rules to block directory traversal patterns (../) in URL parameters, or remediate the vulnerable code by implementing proper input validation and restricting file inclusion paths.
- Consultation3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49360 — 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-49360 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