dbcve.org
AdforestWordPress extension · Scriptsbundle

CVE-2024-11350

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-08
Fix available
A fix is available. Upgrade to 5.1.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
The AdForest theme for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 5.1.6. This is due to the plugin not properly validating a user's identity prior to updating their password through the adforest_reset_password() function. This makes it possible for unauthenticated attackers to change arbitrary user's passwords, including administrators, and leverage that to gain access to their account.

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 confidence

The AdForest WordPress theme contains an insecure password reset function (adforest_reset_password()) that fails to properly validate user identity before allowing password changes. This allows unauthenticated attackers to reset any user's password, including administrators, by exploiting the lack of identity verification in the password reset workflow.

MitigationUpdate the AdForest theme to version 5.1.7 or later which contains the security fix. Until patched, consider disabling the theme or implementing additional server-side authentication controls on password reset endpoints.

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
AdforestWordPress extension
Affected:< 5.1.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. Verify AdForest theme is installed
    Check the WordPress themes directory for the AdForest theme folder, typically at wp-content/themes/adforest. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'template' OR option_name = 'stylesheet';
    Affected if AdForest theme is present in the themes directory or database
  2. Check installed AdForest version
    If the theme is installed, locate the style.css file in the theme directory (wp-content/themes/adforest/style.css) and read the 'Version:' header. Alternatively, check the WordPress database: SELECT * FROM wp_options WHERE option_name LIKE '%theme_version%' OR option_name = 'adforest_theme_version';
    Affected if Version is less than 5.1.7
  3. Confirm adforest_reset_password function exists
    Search the theme files for the function adforest_reset_password. This is typically found in the theme's inc directory or in a file related to user authentication. Use grep or a file search: grep -r "function adforest_reset_password" wp-content/themes/adforest/
    Affected if The function adforest_reset_password is found in the theme code
  4. Verify password reset endpoint is accessible
    Test if the password reset functionality is reachable without authentication. Check if a POST request to the password reset endpoint (commonly at wp-json/adforest/v1/reset-password or similar API route) can be made without authentication. Review theme files for the register_rest_route calls related to password reset.
    Affected if The reset password REST API endpoint is registered and accessible without authentication

The environment is affected if AdForest theme version is below 5.1.7 and the adforest_reset_password function is present and exposed via an unauthenticated endpoint.

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

Update the AdForest theme to version 5.1.7 or later which contains the security fix. Until patched, consider disabling the theme or implementing additional server-side authentication controls on password reset endpoints.

Recommended fix High confidence

AdForest theme version 5.1.7

  1. Backup your WordPress site before making any changes
  2. Download AdForest theme version 5.1.7 from the official source (themeforest.net)
  3. Navigate to Appearance > Themes in WordPress admin dashboard
  4. Deactivate and delete the current AdForest theme
  5. Upload and install version 5.1.7 of the AdForest theme
  6. Activate the new version 5.1.7
  7. Verify the theme version is showing 5.1.7 in the WordPress admin
  8. Consider resetting passwords for administrator accounts as a precautionary measure

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

Fix this in Adforest Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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