dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-25969

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 ThemeHunk Contact Form & Lead Form Elementor Builder allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects Contact Form & Lead Form Elementor Builder: from n/a through 1.8.4.

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

This is a broken access control vulnerability in the ThemeHunk Contact Form & Lead Form Elementor Builder WordPress plugin. The plugin fails to properly validate user authorization before allowing access to certain functions or data, allowing unauthenticated or unauthorized users to perform actions they should not be permitted to execute.

MitigationImplement proper authorization checks (capability checks and nonce verification) on all sensitive functions and verify user permissions before executing any privileged actions.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'ThemeHunk Contact Form' or 'Lead Form Elementor Builder' in the list of installed plugins
    Affected if plugin is present in the plugins list regardless of activation status
  2. Identify installed version
    In the plugins list, click on the plugin name or view the plugin details to find the version number displayed under the plugin name
    Affected if version number falls within the vulnerable version range (unpatched versions)
  3. Check plugin activation status
    In WordPress admin > Plugins, verify whether the ThemeHunk Contact Form plugin is activated
    Affected if plugin is activated - inactive plugins may reduce but not eliminate exposure depending on how the vulnerable code is loaded
  4. Identify vulnerable endpoints/functions
    Review plugin source code in wp-content/plugins/ directory for themehunk-contact-form-lead-form-elementor-builder/ folder, specifically looking for AJAX handlers or public-facing functions that lack capability checks (current_user_can) or nonce verification (wp_verifyNonce)
    Affected if code inspection reveals functions accessible to unauthenticated users without proper authorization validation
  5. Confirm authorization gap
    Test by making an unauthenticated request to suspected vulnerable AJAX actions (typically found via grep search for 'add_action.*wp_ajax_' or 'add_action.*wp_ajax_nopriv_' in plugin files) without providing authentication credentials
    Affected if unauthenticated requests execute privileged actions or return sensitive data that should require authorization

Environment is affected if the ThemeHunk Contact Form plugin is installed, activated, and runs an unpatched version where AJAX or other functions lack proper capability checks and nonce validation, allowing unauthorized access

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

Implement proper authorization checks (capability checks and nonce verification) on all sensitive functions and verify user permissions before executing any privileged actions.

Recommended fix Moderate confidence

Latest version of Contact Form & Lead Form Elementor Builder (version higher than 1.8.4)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Contact Form & Lead Form Elementor Builder' by ThemeHunk
  4. 4. Check the current installed version number
  5. 5. If the installed version is 1.8.4 or lower, update the plugin to the latest available version
  6. 6. Verify the update completed successfully
  7. 7. Test the contact form functionality to ensure the plugin continues to work correctly after the update
Caveat Review plugin settings after upgrade as minor configuration changes may occur with major version updates

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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