dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-3912

MEDIUM · 5.3 CVSS v3.1 Published 2025-04-25
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
The WS Form LITE – Drag & Drop Contact Form Builder for WordPress plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_config' function in all versions up to, and including, 1.10.35. This makes it possible for unauthenticated attackers to read the value of the plugin's settings, including API keys for integrated services.

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 WS Form LITE plugin for WordPress has a missing capability check on its 'get_config' function, allowing unauthenticated attackers to retrieve sensitive configuration data including API keys for integrated services. This is a classic authorization bypass where the function processes requests without verifying user permissions first.

MitigationUpdate to version 1.10.36 or later which includes proper capability checks. Additionally, rotate any API keys that may have been exposed through this vulnerability.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Locate WS Form LITE plugin version
    In WordPress admin, go to Plugins > Installed Plugins > WS Form LITE and note the version number displayed. Alternatively, check the main plugin file (typically wp-content/plugins/ws-form-lite/ws-form.php) for the 'Version' header comment.
    Affected if The installed version is lower than 1.10.36
  2. Identify the get_config function file
    Locate the plugin file containing the 'get_config' function. This is typically in the main plugin PHP file or an AJAX handler file within the ws-form-lite directory.
    Affected if The get_config function exists in the plugin code and is accessible via an AJAX action hook
  3. Verify capability check presence in get_config
    Open the file containing the get_config function and inspect its code. Look for a capability check such as 'current_user_can()' or 'wp_verify_nonce()' at the beginning of the function before any configuration data is processed or returned.
    Affected if No capability check (such as current_user_can) appears before the function retrieves or outputs configuration data
  4. Test AJAX endpoint accessibility
    Examine the WordPress AJAX registration for the get_config function (commonly found via add_action('wp_ajax_nopriv_get_config', ...) or similar). If 'nopriv' is present, the endpoint is accessible to unauthenticated users.
    Affected if The AJAX action for get_config is registered with 'nopriv' prefix, allowing unauthenticated access

You are affected if the installed WS Form LITE version is below 1.10.36 AND the get_config function lacks proper capability checks and is accessible to unauthenticated users.

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 to version 1.10.36 or later which includes proper capability checks. Additionally, rotate any API keys that may have been exposed through this vulnerability.

Recommended fix Moderate confidence

1.10.36

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'WS Form LITE – Drag & Drop Contact Form Builder for WordPress'
  4. Click 'Update now' if an update is available, or manually update to version 1.10.36 or higher
  5. Verify the update was successful by checking the plugin version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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