CVE-2025-31913
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 ApusTheme Ogami ogami allows PHP Local File Inclusion.This issue affects Ogami: from n/a through <= 1.53.
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 PHP Local File Inclusion (LFI) vulnerability exists in the ApusTheme Ogami WordPress theme (versions <= 1.53). The vulnerability allows attackers to include and execute arbitrary PHP files from the local server via improper control of filename parameters in include/require statements, potentially leading to remote 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 Ogami theme is installedList contents of wp-content/themes/ directory and look for a folder named 'ogami', 'apus_ogami', or similar theme folder.Affected if The Ogami theme folder exists in the WordPress themes directory.
-
Determine installed theme versionOpen the theme's style.css file (typically in wp-content/themes/ogami/style.css) and locate the 'Version:' header in the CSS comment block at the top.Affected if The version listed is 1.53 or lower.
-
Check for file inclusion endpointsSearch theme PHP files for include, require, include_once, or require_once statements that use variables in the path (e.g., include($file), require($_GET['param'])). Look in common entry points like functions.php, template files, and any AJAX handlers.Affected if The theme contains file inclusion code that uses unsanitized user-controlled input.
-
Verify web server access to theme filesConfirm the web server process has read access to theme PHP files and that the vulnerable code paths are accessible via HTTP requests (check if the parameter/endpoint is publicly reachable).Affected if The file inclusion parameter is accessible without authentication or can be exploited through another vulnerability.
If the Ogami theme version is 1.53 or lower AND the theme exposes a file inclusion mechanism using unsanitized input, the environment is affected by this LFI 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 dataUpdate the Ogami theme to the latest version if a patch is available. Otherwise, implement input validation and path sanitization on file inclusion parameters, or restrict file permissions to prevent unauthorized PHP file inclusion.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31913 — 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-31913 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