CVE-2026-25458
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 Select-Themes Moments moments allows PHP Local File Inclusion.This issue affects Moments: from n/a through <= 2.2.
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 Select-Themes Moments WordPress theme. The vulnerability allows an attacker to include arbitrary PHP files from the server file system through unsanitized input parameters, 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.
-
Confirm Moments theme is installedInspect the WordPress themes directory at wp-content/themes/ and verify the presence of a folder named 'moments' or 'moments-lite'Affected if The Moments theme folder exists in the WordPress themes directory
-
Identify the installed theme versionOpen the theme's style.css file (wp-content/themes/moments/style.css) and locate the 'Version:' header in the file comments, or check theme.json for the version fieldAffected if The version number returned matches or falls within the affected range (all versions prior to patch)
-
Locate file inclusion functions in theme codeSearch theme PHP files for include, include_once, require, or require_once statements that use variables without sanitization - grep -r 'include.*\$' wp-content/themes/moments/Affected if Theme files contain dynamic file inclusion using unsanitized user input (e.g., include($_GET['file']) )
-
Identify the vulnerable parameterExamine identified include statements to determine which GET/POST parameter controls the file path (common names: file, template, page, lang, include)Affected if A parameter accepts user-controlled input and is used directly in file inclusion without validation
-
Verify the vulnerability is exploitableSend a test HTTP request with a benign path such as ?param=../../../../wp-config.php (using the identified parameter name) to verify the application processes the pathAffected if The application returns content from the requested file or exposes file paths, indicating the parameter is not sanitized
Your environment is affected if the Moments theme is installed and contains dynamic file inclusion code that uses unsanitized user input, allowing path traversal via HTTP 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 Moments theme to a patched version once available. If no update exists, implement input validation/sanitization on file inclusion parameters and consider deploying a WAF rule to block directory traversal patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25458 — 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-2026-25458 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