HeartstarWordPress extension · Axiomthemes
CVE-2025-60046
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 axiomthemes HeartStar heartstar allows PHP Local File Inclusion.This issue affects HeartStar: from n/a through <= 1.0.14.
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 HeartStar theme where user-supplied input is not properly validated before being used in include/require statements. An attacker could manipulate file path parameters to read sensitive files from the server or potentially execute arbitrary PHP code if they can write files to accessible locations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
HeartstarWordPress extension
<= 1.0.14CVSS 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.
-
Check Heartstar theme versionOpen the theme's style.css file (typically at /wp-content/themes/heartstar/style.css) and look for the 'Version:' header in the theme comment block at the top. Compare this version number against the affected range (<= 1.0.14).Affected if The installed version is 1.0.14 or lower.
-
Identify file inclusion code patternsSearch the theme directory (especially PHP files in the root and includes/ folder) for include, require, include_once, or require_once statements that use superglobal input ($_GET, $_POST, $_REQUEST) directly as the path, for example: include($_GET['file']).Affected if Such code patterns exist without proper input validation (basename, realpath, whitelist checks).
-
Inspect the vulnerable parameter usageExamine any PHP files that accept file path parameters (commonly named 'file', 'page', 'template', 'include', or similar) and pass them directly to include/require functions. Look for patterns like: include($_REQUEST['file']); or require($theme_dir . $_GET['page']);Affected if The parameter is used directly in file inclusion functions without sanitization or whitelist validation.
-
Check for directory traversal preventionVerify that any file inclusion code that uses user input includes security checks such as basename(), realpath(), or explicit whitelist validation before the include/require statement.Affected if No such sanitization functions are present before file inclusion calls.
A user is affected if the Heartstar theme version is 1.0.14 or lower AND the theme contains file inclusion code that uses unsanitized user-supplied input from URL 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 dataImplement strict whitelist-based input validation on all file inclusion parameters, ensuring only allowed files/directories can be included. Use basename() and realpath() to sanitize paths and prevent directory traversal attacks.
Fix this in Heartstar
Scoped from the published advisory
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60046 — 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-60046 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