CVE-2025-49362
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 Gracioza gracioza allows PHP Local File Inclusion.This issue affects Gracioza: 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 Gracioza WordPress theme by AncoraThemes contains a PHP Local File Inclusion (LFI) vulnerability. The vulnerability stems from improper control of filenames in include/require statements, allowing attackers to manipulate file paths and include arbitrary local files. This can lead to sensitive information disclosure or potentially remote code execution depending on server configuration.
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 Gracioza theme is installedCheck the WordPress themes directory at /wp-content/themes/ for a gracioza folder, or view installed themes via WordPress dashboard under Appearance > ThemesAffected if The gracioza theme folder exists in the WordPress themes directory
-
Determine Gracioza theme versionOpen the style.css file within the gracioza theme folder and look for the 'Version:' field in the theme header comment blockAffected if The installed version matches or falls within the vulnerable version range for this CVE
-
Locate file inclusion code in theme PHP filesSearch all PHP files within the gracioza theme folder for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST directly without sanitizationAffected if Code contains file inclusion statements that directly use unsanitized user input in the file path
-
Verify the vulnerable parameter is accessibleAttempt to access the identified vulnerable PHP file with a test file path parameter (e.g., ?file=../../../../wp-config.php) via GET or POST request to see if local file inclusion occursAffected if The server returns contents of the specified file, confirming the LFI vulnerability is exploitable
A user is affected if the Gracioza theme is installed, the version is within the vulnerable range, and the theme contains unsafe file inclusion code that uses user-supplied input without validation.
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 input validation and sanitization on all file inclusion parameters, use allowlists for permitted files, and avoid using user-supplied input directly in include/require statements. Consider upgrading to a patched version if available from the vendor.
- 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-49362 — 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-49362 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