CVE-2025-49282
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 unfoldwp Magze magze allows PHP Local File Inclusion.This issue affects Magze: from n/a through <= 1.0.9.
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 confidenceLocal File Inclusion vulnerability in the Magze theme allows attackers to manipulate file inclusion paths through insufficient input validation on include/require statements. An unauthenticated attacker could potentially include arbitrary PHP files from the server, 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 Magze theme installationSearch your web server for files containing 'Magze' theme code, typically found in themes/magze/ directory. Look for theme style.css header or functions.php files that reference the theme name.Affected if Magze theme files are present on the server
-
Locate include/require statements using variable inputSearch PHP files within the Magze theme directory for patterns like 'include($_', 'require($_', 'include_once($_', 'require_once($_' where user-supplied parameters are used directly in inclusion functions.Affected if Direct use of $_GET, $_POST, or $_REQUEST variables in include/require statements is found without sanitization
-
Verify lack of input validation on file inclusion parametersExamine the code around identified include/require statements. Check whether parameters used in file inclusion are validated using functions like basename(), realpath(), or allowlist validation before being used.Affected if No basename(), realpath(), or allowlist validation is applied to file inclusion parameters before the include/require call
-
Confirm the vulnerable endpoints are accessible without authenticationDetermine if the PHP files containing the vulnerable include/require logic can be accessed directly via HTTP requests without requiring login or session authentication.Affected if The file inclusion functionality is reachable without authentication (no login/session check required)
-
Check for arbitrary file read capabilityTest (in a safe, non-production manner) whether parameters passed to include/require can be manipulated to point to files outside the intended theme directory, such as ../../ etc.Affected if Path traversal sequences in file inclusion parameters are not blocked and allow accessing files outside the theme directory
A user is affected if the Magze theme is installed AND its PHP files contain include/require statements using unsanitized user input that can be accessed without authentication, allowing path traversal to include arbitrary PHP files.
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 dataImplement strict allowlist-based validation for file inclusion parameters using basename() and realpath() functions, or refactor to use fixed inclusion paths without user-controlled input.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49282 — 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-49282 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