dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-48835

HIGH · 7.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Broken Access Control in Contact Form by WPForms <= 1.10.0.4 versions.

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

Unauthenticated broken access control vulnerability in the Contact Form by WPForms WordPress plugin versions 1.10.0.4 and below allows unauthenticated attackers to access functionality that should require proper authorization.

MitigationUpdate Contact Form by WPForms plugin to a version newer than 1.10.0.4.

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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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. Verify WPForms plugin is installed
    Check your WordPress installation for the Contact Form by WPForms plugin. In WordPress admin, go to Plugins > Installed Plugins and look for 'Contact Form by WPForms' or check the /wp-content/plugins/ directory for the wpforms folder.
    Affected if The WPForms plugin is present in the WordPress installation
  2. Determine installed WPForms version
    In WordPress admin, go to Plugins > Installed Plugins > Contact Form by WPForms and view the version number displayed. Alternatively, check the main plugin file header in wpforms/wpforms.php for the 'Version' tag.
    Affected if The installed version is 1.10.0.4 or lower
  3. Compare version against affected range
    Compare your installed version number to the affected range: versions 1.10.0.4 and below are vulnerable. Any version at or below 1.10.0.4 is affected.
    Affected if The installed version is 1.10.0.4 or any version lower than 1.10.0.4
  4. Test unauthenticated access to protected functionality
    Attempt to access WPForms administrative functions or form submission endpoints without logging in. Send a request to a typical WPForms endpoint (such as form processing or admin-ajax actions used by the plugin) while unauthenticated and observe if the server responds without returning an authorization error.
    Affected if Unauthenticated requests successfully access functionality that should require logged-in status

You are affected if the Contact Form by WPForms plugin is installed and the version is 1.10.0.4 or below, or if unprotected plugin functionality is accessible without authentication.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Contact Form by WPForms plugin to a version newer than 1.10.0.4.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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