dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-25320

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
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 Cool Plugins Elementor Contact Form DB sb-elementor-contact-form-db allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Elementor Contact Form DB: from n/a through <= 2.1.3.

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

Missing authorization in the Cool Plugins Elementor Contact Form DB plugin allows unauthenticated or low-privilege users to access or manipulate contact form submissions they should not have access to, due to incorrectly configured access control security levels.

MitigationImplement proper capability checks (e.g., current_user_can()) and nonce validation on all sensitive endpoints and data access functions within the plugin to enforce role-based access controls.

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. Confirm plugin installation
    Check if the Cool Plugins Elementor Contact Form DB plugin is installed in the WordPress plugins directory (wp-content/plugins/) or via WP-CLI: wp plugin list --name='elementor-contact-form-db'
    Affected if Plugin is installed and active in WordPress
  2. Identify installed version
    Check the plugin version in WordPress admin under Plugins > Installed Plugins, or read the main plugin PHP file header for the 'Version' tag, or use WP-CLI: wp plugin get elementor-contact-form-db --format=json
    Affected if Version is at or below the affected version range for this CVE (contact form DB plugin versions prior to vendor patch)
  3. Test unauthenticated submission access
    Send a direct HTTP request to common plugin AJAX endpoints or form submission handlers (e.g., /wp-admin/admin-ajax.php?action=cfdb_submit or similar) without providing authentication cookies or valid nonces, observing if the server accepts the request
    Affected if Server accepts and processes the request without requiring authentication or valid capability checks
  4. Verify role-based access controls
    Create or use a low-privilege WordPress user account (e.g., Subscriber role) and attempt to access form submission data via plugin admin pages or AJAX actions, observing whether access is improperly granted
    Affected if Low-privilege users can view or modify contact form submissions they did not submit
  5. Inspect plugin capability configuration
    Check the plugin settings in WordPress admin panel for any security level or access control options (sometimes labeled as 'Who can view submissions', 'Access Level', or similar), and review plugin PHP code for missing current_user_can() checks on sensitive functions
    Affected if Plugin lacks proper capability checks or exposes admin functionality to lower-privileged roles

If the Cool Plugins Elementor Contact Form DB plugin is installed and low-privilege or unauthenticated users can access/modify form submissions without proper authorization, the environment is affected by this CVE.

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 capability checks (e.g., current_user_can()) and nonce validation on all sensitive endpoints and data access functions within the plugin to enforce role-based access controls.

Recommended fix Moderate confidence

latest version beyond 2.1.3 (verify the most recent release on WordPress.org or the vendor's site)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Elementor Contact Form DB' by Cool Plugins
  4. 4. Check the current installed version
  5. 5. Update the plugin to the latest available version that addresses the authorization vulnerability
  6. 6. Verify the update was successful
  7. 7. Test the contact form submission functionality to ensure the plugin still works correctly

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 / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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