dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-24747

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 favethemes Houzez houzez.This issue affects Houzez: from n/a through <= 3.4.0.

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 · low confidence

Missing Authorization vulnerability in the Houzez WordPress theme allows attackers to access sensitive functionality or perform actions without proper permission checks. The specific affected endpoints or actions are not detailed in the available information, but such vulnerabilities typically allow lower-privileged or unauthenticated users to execute operations that should require higher privileges.

MitigationUpdate Houzez theme to version 3.4.1 or later if a patched version is available. If no patch exists, implement proper capability checks and nonce verification on all sensitive AJAX actions and admin functions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 the installed Houzez theme version
    Navigate to Appearance > Themes in WordPress admin dashboard. Locate the Houzez theme and note the version number displayed, or check the style.css file in the theme directory for the 'Version:' header.
    Affected if The installed version is earlier than 3.4.1 or the version cannot be determined (older unpatched versions).
  2. Inspect AJAX actions for missing capability checks
    Review the theme's functions.php and any included PHP files for AJAX handlers (wp_ajax_ and wp_ajax_nopriv_ hooks). Check if each handler includes current_user_can() or similar capability checks before executing sensitive operations.
    Affected if Any AJAX action handling sensitive operations lacks proper capability verification (no current_user_can() check before executing).
  3. Check admin function authorization
    Examine admin-side functions in the theme, particularly those hooked to admin_menu, admin_init, or other admin actions. Verify that each sensitive function includes permission checks using current_user_can() or role verification.
    Affected if Admin functions that modify settings, user data, or system configuration lack authorization checks.
  4. Review nonce verification on sensitive actions
    Look for wp_verify_nonce() or check_admin_referer() calls in AJAX handlers and form processing functions. Verify that nonce validation is present and correctly implemented for all state-changing operations.
    Affected if Sensitive actions (data modification, settings changes) lack nonce verification or use weak/incorrect nonce validation.

The environment is affected if the installed Houzez theme version is earlier than 3.4.1 AND the theme contains AJAX handlers or admin functions that perform sensitive operations without verifying user capabilities or validating nonces.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Houzez theme to version 3.4.1 or later if a patched version is available. If no patch exists, implement proper capability checks and nonce verification on all sensitive AJAX actions and admin functions.

Recommended fix Moderate confidence

Houzez version greater than 3.4.0 (latest available version)

  1. 1. Log in to the WordPress admin dashboard where the Houzez theme is installed
  2. 2. Navigate to Appearance > Themes
  3. 3. Check the current version of the Houzez theme by clicking on the theme details
  4. 4. Verify if an update is available for the Houzez theme
  5. 5. If an update is available, back up the current WordPress site (database and files)
  6. 6. Update the Houzez theme to the latest available version which should contain the fix for CVE-2025-24747
  7. 7. After updating, verify the site functions correctly and test that the authorization checks are now in place
Caveat Check Houzez changelog for any breaking changes between 3.4.0 and the target version before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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