dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-14574

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-09
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 weDocs plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.1.15 via the `/wp-json/wp/v2/docs/settings` REST API endpoint. This makes it possible for unauthenticated attackers to extract sensitive data including third party services API keys.

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 weDocs WordPress plugin exposes sensitive settings including third-party API keys through the unprotected REST API endpoint /wp-json/wp/v2/docs/settings. This endpoint is accessible to unauthenticated users, allowing any visitor to retrieve configuration data that should be restricted.

MitigationUpdate the weDocs plugin to version 2.1.16 or later which should add proper authentication to the settings endpoint. Alternatively, disable the REST API endpoint or restrict access via web server configuration until the patch is applied.

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. Verify weDocs plugin is installed
    Log in to WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'weDocs' in the list of active plugins.
    Affected if weDocs plugin is installed and active
  2. Check installed weDocs version
    In the WordPress admin, go to Plugins > Installed Plugins. Find weDocs and note the version number displayed under the plugin name. Compare this to version 2.1.16.
    Affected if weDocs version is lower than 2.1.16
  3. Test unauthenticated access to the vulnerable endpoint
    Open a web browser or use a tool like curl in a terminal. Navigate to the URL: https://your-site.com/wp-json/wp/v2/docs/settings (replace 'your-site.com' with your actual WordPress site URL). Observe whether the endpoint returns JSON data without requiring any login credentials.
    Affected if The endpoint returns HTTP 200 and displays JSON data containing settings or API keys without any authentication prompt
  4. Inspect returned settings for sensitive data
    Examine the JSON response from the previous step. Look for fields that may contain API keys, secret tokens, passwords, or other configuration values that should be restricted.
    Affected if The response includes any sensitive configuration data such as API keys, tokens, or credentials

A user is affected if weDocs plugin versions below 2.1.16 are installed and the /wp-json/wp/v2/docs/settings endpoint returns sensitive data without requiring 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the weDocs plugin to version 2.1.16 or later which should add proper authentication to the settings endpoint. Alternatively, disable the REST API endpoint or restrict access via web server configuration until the patch is applied.

Recommended fix Moderate confidence

Latest version of weDocs plugin (newer than 2.1.15)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the weDocs plugin
  4. If update available, click 'Update Now' to install the latest version
  5. After updating, verify the `/wp-json/wp/v2/docs/settings` endpoint no longer exposes sensitive data for unauthenticated users

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-2025-14574 — 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-14574 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