Good MoodWordPress extension · Axiomthemes
CVE-2025-58894
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 Good Mood good-mood allows PHP Local File Inclusion.This issue affects Good Mood: from n/a through <= 1.16.
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 Good Mood WordPress theme by axiomthemes contains a PHP Local File Inclusion (LFI) vulnerability where user-supplied input is improperly validated before being used in include/require statements. An attacker could exploit this to include arbitrary PHP files from the server, potentially leading to remote code execution if they can upload files or access sensitive configuration files.
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
Good MoodWordPress extension
<= 1.16CVSS 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.
-
Confirm Good Mood theme installationNavigate to Appearance > Themes in WordPress admin panel, or inspect /wp-content/themes/ directory for a folder named 'good-mood' or similar axiomthemes theme folderAffected if The Good Mood theme by axiomthemes is present in the WordPress installation
-
Identify theme versionCheck the style.css file within the theme folder for the 'Version:' header, or look in theme.json for version informationAffected if The installed version is 1.16 or lower, or if no version is found but the theme is present
-
Locate file inclusion pointsSearch theme PHP files for include, require, include_once, or require_once statements that use variables (e.g., include($file), require($_GET['param'])) without proper validationAffected if Any PHP files in the theme contain dynamic file inclusion using user-supplied input (GET/POST parameters) without sanitization
-
Inspect ajax or callback handlersExamine files like functions.php, ajax-handlers.php, or any file referenced in add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...') calls for file inclusion logicAffected if Ajax handlers accept file path parameters and pass them directly to include/require statements
-
Check template files for include logicReview template files that might accept a 'template' or 'file' GET parameter and use it in include/require statementsAffected if Any template file uses a parameter like ?file= or ?template= in include/require without validation
A user is affected if the Good Mood theme version is 1.16 or lower AND the theme contains PHP files with dynamic file inclusion using unsanitized user input.
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 Good Mood theme; if no patch is available, implement strict input validation and whitelist-based filtering on any file inclusion parameters, and ensure all user-uploaded files are stored outside the web root.
Fix this in Good Mood
Scoped from the published advisory
- 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-58894 — 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-58894 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