dbcve.org
MakeaholicWordPress extension · Thememove

CVE-2025-58210

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-03
Fix available
A fix is available. Upgrade to 1.8.7 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
Missing Authorization vulnerability in ThemeMove Makeaholic makeaholic allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Makeaholic: from n/a through <= 1.8.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 · moderate confidence

A missing authorization vulnerability exists in the ThemeMove Makeaholic WordPress theme (versions <= 1.8.5) where incorrectly configured access control security levels allow unauthenticated or unauthorized users to access sensitive functions or data that should be restricted.

MitigationImplement proper authorization checks on all sensitive functions and endpoints within the theme, verifying user permissions before executing privileged operations.

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.7

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. Confirm Makeaholic theme is installed
    Locate the theme files in your WordPress installation under wp-content/themes/makeaholic or check via WordPress admin under Appearance > Themes
    Affected if The Makeaholic theme by Thememove is present in the WordPress themes directory
  2. Identify the installed version
    Open the style.css file in wp-content/themes/makeaholic and locate the 'Version:' field in the file header comment
    Affected if The version number listed is lower than 1.8.7 (for example: 1.8.6, 1.8.5, 1.0, etc.)
  3. Check if theme is actively in use
    In WordPress admin, go to Appearance > Themes and verify which theme is currently activated and applied to the site
    Affected if The Makeaholic theme is the active theme on the WordPress site
  4. Audit publicly accessible theme functions
    Review theme PHP files in wp-content/themes/makeaholic for any AJAX handlers, admin-ajax.php hooks, or custom endpoints that lack current_user_can() or role verification checks
    Affected if Theme files contain functionality accessible to unauthenticated or unauthorized users without proper capability checks
  5. Review admin access controls
    Examine theme options panels and settings pages to determine if they enforce WordPress user role restrictions (administrator, editor, author)
    Affected if Theme settings or administrative functions can be accessed or modified by low-privileged users (subscribers, guests) who should not have access

A user is affected if the Makeaholic theme version is below 1.8.7 AND the theme is actively installed on their WordPress site, particularly if unauthorized access to sensitive theme functions is possible.

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.7 or later
Fixed in 1.8.7
Interim mitigation

Implement proper authorization checks on all sensitive functions and endpoints within the theme, verifying user permissions before executing privileged operations.

Recommended fix High confidence

Makeaholic theme version 1.8.7

  1. 1. Backup your WordPress site before making any changes
  2. 2. Navigate to Appearance > Themes in your WordPress admin dashboard
  3. 3. If you have the Makeaholic theme installed, check the current version number
  4. 4. Download Makeaholic version 1.8.7 or later from a trusted source (ThemeMove or authorized marketplace)
  5. 5. Upload and install the updated theme, replacing the vulnerable version
  6. 6. Verify the theme version has been updated to 1.8.7 or higher
  7. 7. Test your site functionality to ensure the theme update did not break any features
Caveat Review theme settings after upgrade as some configurations may need reapplication

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

Fix this in Makeaholic Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-58210 — 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-58210 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