dbcve.org
AdforestWordPress extension · Scriptsbundle

CVE-2024-11349

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-21
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 authentication bypass in all versions up to, and including, 5.1.6. This is due to the plugin not properly verifying a user's identity prior to authenticating them through the sb_login_user_with_otp_fun() function. This makes it possible for unauthenticated attackers to log in as arbitrary users, including administrators.

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 authentication bypass vulnerability in the sb_login_user_with_otp_fun() function in versions up to 5.1.6. The function fails to properly verify user identity before completing authentication, allowing unauthenticated attackers to log in as any user, including administrators, by manipulating the OTP verification flow.

MitigationUpdate the AdForest theme to version 5.1.7 or later. If immediate patching is not possible, disable OTP-based authentication and enforce strong password authentication as a temporary workaround.

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. Identify AdForest theme installation
    Check your WordPress installation for the AdForest theme. In the wp-content/themes/adforest/ directory, open style.css and look for the 'Version:' declaration in the file header.
    Affected if The theme is installed and the version number is below 5.1.7 (for example, 5.1.6, 5.1.5, etc.)
  2. Confirm OTP authentication is enabled
    Log into WordPress admin, navigate to AdForest theme settings, and look for OTP-related configuration options under authentication or login settings. Check if OTP-based login is activated for user authentication.
    Affected if OTP-based login functionality is enabled in the theme settings, making the vulnerable sb_login_user_with_otp_fun() function accessible.
  3. Verify the vulnerable endpoint is accessible
    Check if your site exposes the OTP login endpoint. Look for routes containing 'otp-login', 'sb-otp-login', or similar patterns in your web server logs or by inspecting the theme's ajax handlers for the sb_login_user_with_otp_fun function.
    Affected if The OTP login functionality is publicly accessible without requiring prior authentication, allowing the bypass to be exploited.

Your environment is affected if the AdForest theme version is below 5.1.7 AND OTP-based authentication is enabled, allowing unauthenticated attackers to potentially log in as any user by manipulating the OTP verification flow.

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. If immediate patching is not possible, disable OTP-based authentication and enforce strong password authentication as a temporary workaround.

Recommended fix High confidence

AdForest theme version 5.1.7

  1. Create a full backup of the WordPress site, including database and files, before making any changes
  2. Log in to the WordPress admin dashboard and navigate to Appearance > Themes
  3. Deactivate the current AdForest theme installation
  4. Delete the existing AdForest theme if the platform allows direct updates, or proceed to update
  5. If updating directly: navigate to the theme's update option or upload AdForest version 5.1.7 from themeforest.net
  6. Activate the updated AdForest 5.1.7 theme
  7. Verify the theme version shows 5.1.7 in Appearance > Themes
  8. Test the OTP login functionality to confirm the authentication mechanism is working correctly

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

Fix this in Adforest Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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