dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-1729

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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, 6.0.12. 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. The function fails to properly verify user identity before authenticating them, allowing unauthenticated attackers to log in as any user, including administrators.

MitigationUpdate the AdForest theme to version 6.0.13 or later if available. If no patched version exists, disable the theme or the affected login function until a fix is released. Review access logs for suspicious admin logins.

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
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 AdForest theme installation
    Navigate to wp-content/themes/ in your WordPress installation directory and verify the adforest theme folder exists. Alternatively, check Appearance > Themes in WordPress admin dashboard for an 'AdForest' theme entry.
    Affected if The AdForest theme is present in the themes directory or listed in the WordPress admin themes page.
  2. Identify installed AdForest version
    Open the style.css file within the adforest theme folder (wp-content/themes/adforest/style.css) and locate the 'Version:' comment at the top of the file. Alternatively, check the theme's functions.php for a version definition.
    Affected if The version number found is lower than 6.0.13 (for example, 6.0.12, 6.0.10, etc.) or if no version is displayed and the theme has not been updated recently.
  3. Verify OTP login functionality is enabled
    Log in to WordPress admin dashboard, navigate to AdForest Theme Settings > General Settings or Login/Register settings, and check if the OTP-based login option is enabled or active.
    Affected if The OTP login feature (sb_login_user_with_otp_fun) is turned on in the theme settings, making the vulnerable function accessible.
  4. Review access logs for unauthorized admin logins
    Check your web server access logs (typically in /var/log/apache2/ or /var/log/nginx/) or use a WordPress security plugin to review login history. Look for successful logins to administrator accounts from unfamiliar IP addresses or at unusual times.
    Affected if There are admin-level logins that you do not recognize, especially from IP addresses not associated with legitimate administrators.

You are affected if the AdForest theme is installed with a version lower than 6.0.13 and the OTP login feature is enabled, or if you discover unauthorized admin account access in your logs.

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 the AdForest theme to version 6.0.13 or later if available. If no patched version exists, disable the theme or the affected login function until a fix is released. Review access logs for suspicious admin logins.

Recommended fix Moderate confidence

AdForest theme version > 6.0.12 (latest available version)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Appearance > Themes
  3. 3. Locate the AdForest theme
  4. 4. Check for available updates to the theme
  5. 5. Update to the latest available version of AdForest theme (version higher than 6.0.12)
  6. 6. Verify the update was successful by confirming the new version number
  7. 7. Test the login functionality to ensure the OTP authentication is working correctly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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