CVE-2025-49258
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 thembay Maia maia allows PHP Local File Inclusion.This issue affects Maia: from n/a through <= 1.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 · high confidenceA PHP Local File Inclusion vulnerability exists in thembay Maia plugin/theme where user-supplied input is used in include/require statements without proper validation or sanitization, allowing attackers to include arbitrary PHP files from the server file system.
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 thembay Maia installationSearch the web server document root for files or directories named 'maia', 'thembay', or look for theme/plugin folders containing 'maia' in the name. Check wp-content/themes/ or wp-content/plugins/ if this is a WordPress environment, or application/plugin/theme directories for other PHP applications.Affected if The thembay Maia plugin or theme is present in the environment
-
Locate include/require statementsSearch the codebase for include, include_once, require, or require_once statements that use variables or parameters without sanitization. Use grep or similar: grep -r 'include\|require' --include='*.php' in the maia directory. Look for patterns like 'include($_GET[...])' or 'require($variable)'Affected if User-controllable input is used directly in include/require statements without validation
-
Inspect file inclusion parametersExamine any PHP files that handle request parameters (GET, POST, COOKIE) and pass them to include/require statements. Check for parameters that might control file paths, such as 'file', 'page', 'template', 'path', 'dir', or similar.Affected if Parameters from HTTP requests are used in file inclusion logic without whitelist validation or path traversal checks
-
Verify input validation existsReview the code around include/require statements to determine if there is any validation: check for file existence checks, whitelist arrays, basename() or realpath() usage, or regex validation of the input before it's used in inclusion.Affected if No input validation, whitelisting, or path sanitization is present on parameters used in file inclusion
-
Check for patch availabilityContact thembay or check their official channels for a patched version of the Maia plugin/theme. Compare any installed version number against official release notes.Affected if No patched version is available from the vendor and vulnerable code patterns are present
The environment is affected if the thembay Maia plugin/theme is installed AND user-supplied input flows into include/require statements without validation or sanitization.
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 if available; otherwise, audit and fix all include/require statements to use whitelisted file paths and implement strict input validation on any parameters used for file inclusion.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49258 — 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-49258 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