CVE-2025-39360
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 everestthemes Grace Mag grace-mag allows PHP Local File Inclusion.This issue affects Grace Mag: from n/a through <= 1.1.5.
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 confidenceThe Grace Mag WordPress theme <= 1.1.5 contains a PHP Local File Inclusion (LFI) vulnerability due to improper control of filenames in include/require statements. Attackers can manipulate input parameters to include arbitrary PHP files from the local filesystem, potentially leading to remote code execution if they can upload files or access sensitive files.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 Grace Mag theme is installedNavigate to wp-content/themes/ and check for a folder named 'grace-mag' or similar variantAffected if The grace-mag theme directory exists in the WordPress themes folder
-
Determine the installed theme versionOpen the theme's style.css file (typically in wp-content/themes/grace-mag/style.css) and locate the 'Version:' header in the comment block at the topAffected if The version listed is 1.1.5 or lower, or if no version is specified and the theme appears outdated
-
Search for vulnerable include/require patternsExamine PHP files in the theme directory for include(), require(), include_once(), or require_once() statements that use unsanitized input from $_GET, $_POST, $_REQUEST, or similar superglobals as part of the file pathAffected if Any PHP file contains include/require statements using raw user input without validation (e.g., include($_GET['page']); or require($path . $_REQUEST['file']);)
-
Identify exposed file inclusion parametersTest GET/POST parameters used in the theme's PHP files by reviewing source code or using a web proxy to observe which parameters are passed to include/require functionsAffected if Parameters accepting file paths are accessible via URL or form input without proper sanitization
-
Check for auxiliary file upload capabilitiesReview whether the theme or associated plugins allow file uploads to directories accessible from the web server (wp-content/uploads/, temp directories, etc.)Affected if Users can upload files to the server, which could be combined with LFI to achieve remote code execution
A user is affected if the Grace Mag theme version is 1.1.5 or lower AND the theme contains include/require statements that use unsanitized user-supplied input, particularly if file upload functionality exists on the site.
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 of the Grace Mag theme that properly validates and sanitizes all file path inputs used in include/require statements, or implement input validation/wrapper functions to prevent path traversal.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-39360 — 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-39360 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