dbcve.org
MakeaholicWordPress extension · Thememove

CVE-2025-54700

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-14
Fix available
A fix is available. Upgrade to 1.8.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in ThemeMove Makeaholic makeaholic allows PHP Local File Inclusion.This issue affects Makeaholic: from n/a through <= 1.8.4.

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 confidence

A PHP Local File Inclusion (LFI) vulnerability exists in the ThemeMove Makeaholic theme (versions <= 1.8.4). The vulnerability allows attackers to manipulate file path parameters in include/require statements to execute arbitrary PHP code by including malicious local files or reading sensitive system files.

MitigationUpdate the Makeaholic theme to the latest patched version immediately. If no patch is available, replace the theme with a secure alternative or disable it entirely until a fix is released.

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
MakeaholicWordPress extension
Affected:< 1.8.5

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the Makeaholic theme is installed
    Inspect your WordPress theme directory (wp-content/themes/) and look for a folder named 'makeaholic' or thememove-makephpolic. Check theme style.css for the theme name and version header.
    Affected if The Makeaholic theme folder exists in the themes directory.
  2. Determine the installed theme version
    Open the style.css file within the Makeaholic theme folder and locate the 'Version:' header in the theme comment block at the top.
    Affected if The version listed is 1.8.4 or lower.
  3. Search for vulnerable include/require patterns
    Review PHP files in the theme for include(), require(), include_once(), or require_once() statements that accept variable parameters without proper sanitization, particularly those handling file path arguments.
    Affected if Dynamic file inclusion statements are found that use unsanitized user input as file paths.
  4. Check if theme templates expose file path parameters
    Examine template files for GET or POST parameters (such as 'file', 'path', 'template', 'page', 'include') that are used directly in include/require statements without validation.
    Affected if URL parameters are used to control included files without validation checks.

A user is affected if they have the Makeaholic theme installed with version 1.8.4 or lower AND the theme exposes file inclusion functionality via URL parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 1.8.5 or later
Fixed in 1.8.5
Interim mitigation

Update the Makeaholic theme to the latest patched version immediately. If no patch is available, replace the theme with a secure alternative or disable it entirely until a fix is released.

Recommended fix Moderate confidence

1.8.5

  1. Create a complete backup of your WordPress site (files and database) before proceeding
  2. Obtain Makeaholic theme version 1.8.5 from ThemeMove or an authorized marketplace
  3. Log into the WordPress admin dashboard
  4. If Makeaholic is currently the active theme, temporarily activate a different theme
  5. Navigate to Appearance > Themes
  6. Delete the existing Makeaholic theme installation
  7. Upload and install the Makeaholic 1.8.5 theme package
  8. Activate the updated Makeaholic 1.8.5 theme

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Makeaholic Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54700 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54700 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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