dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-25035

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 Fullworks Quick Contact Form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Quick Contact Form : from n/a through 8.0.3.1.

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

The Fullworks Quick Contact Form WordPress plugin versions up to 8.0.3.1 contain a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This likely enables authenticated users (possibly with low-privilege roles like subscriber) to access or modify functionality they should not have permission to access.

MitigationUpdate the Quick Contact Form plugin to the latest version (8.0.4 or higher) which contains the authorization fix. If immediate update is not possible, disable the plugin until patched.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 the plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Quick Contact Form' or check the filesystem at wp-content/plugins/ for a directory named 'quick-contact-form' or similar fullworks plugin directory
    Affected if The plugin directory exists in wp-content/plugins/
  2. Determine the installed plugin version
    In WordPress admin > Plugins, find the Quick Contact Form plugin and read the version number from the plugin description, or open the main plugin PHP file and look for the 'Version' header comment
    Affected if Version is 8.0.3.1 or lower (any version up to and including 8.0.3.1)
  3. Identify existing user roles on the site
    Go to WordPress admin > Users and review the list of registered users. Note any accounts assigned the 'Subscriber' role or other low-privilege roles
    Affected if At least one user with Subscriber role or low-privilege role exists on the site
  4. Check if adminajax or REST endpoints are accessible to low-privilege users
    Examine the plugin code for adminajax actions or REST API routes. Look for 'add_action' calls on admin-ajax.php or 'register_rest_route' calls that do NOT include capability checks like 'manage_options' or 'edit_posts' before the callback function
    Affected if Plugin registers AJAX or REST endpoints without capability/authorization checks (no current_user_capability or similar validation before executing sensitive functions)

You are affected if the Quick Contact Form plugin is installed at version 8.0.3.1 or lower AND low-privilege user roles (like Subscriber) exist on the site AND the plugin exposes endpoints without proper authorization checks.

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 Quick Contact Form plugin to the latest version (8.0.4 or higher) which contains the authorization fix. If immediate update is not possible, disable the plugin until patched.

Recommended fix Moderate confidence

Latest available version of Quick Contact Form (beyond 8.0.3.1)

  1. 1. Update the Fullworks Quick Contact Form plugin to the latest available version beyond 8.0.3.1
  2. 2. After updating, verify that the plugin's access control settings are properly configured according to your security requirements
  3. 3. Test that the contact form functionality works correctly after the update
  4. 4. Review user roles and permissions to ensure only authorized users can access administrative functions

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

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-2023-25035 — 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-25035 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