dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-12825

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-17
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 User Registration Using Contact Form 7 plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'get_cf7_form_data' function in all versions up to, and including, 2.5. This makes it possible for unauthenticated attackers to retrieve form settings which includes Facebook app secrets.

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 User Registration Using Contact Form 7 WordPress plugin lacks a capability check on the 'get_cf7_form_data' function, allowing unauthenticated attackers to directly access this function and retrieve sensitive form configuration data including Facebook app secrets. This is a broken access control vulnerability where the function trusts user input without verifying authorization.

MitigationUpdate the plugin to version 2.6 or later which includes the missing capability check. Alternatively, disable the plugin until an update is available. Review access logs for unauthorized access attempts to the affected endpoint.

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. Identify plugin installation and version
    In WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'User Registration Using Contact Form 7'. The version number is displayed under the plugin name. Alternatively, check the plugin files in wp-content/plugins/user-registration-using-contact-form-7/ for a version marker.
    Affected if The plugin is installed and the version is below 2.6
  2. Verify unauthenticated access to vulnerable function
    Send a direct HTTP request to the AJAX endpoint that calls get_cf7_form_data. This typically targets wp-admin/admin-ajax.php with action parameter 'cf7_user_registration_get_form_data' or similar, without providing any authentication cookies or nonce tokens.
    Affected if The endpoint returns sensitive form configuration data (including Facebook app secrets) without requiring login credentials
  3. Inspect the plugin source code for capability check
    Examine the PHP file containing the get_cf7_form_data function (usually in includes/ or main plugin file). Look for a current_user_can() or similar authorization check before the function logic.
    Affected if No capability check (current_user_can, check_ajax_referer, etc.) is present before the function processes the request
  4. Review access logs for exploitation attempts
    Search web server access logs (Apache, Nginx) for requests to admin-ajax.php with the specific action parameter used by this plugin, especially from external IP addresses without corresponding admin session cookies.
    Affected if Log entries show unauthenticated requests to the affected endpoint from unknown IP addresses

The environment is affected if the plugin version is below 2.6 and the get_cf7_form_data function can be accessed without authentication, allowing exposure of sensitive configuration data.

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 plugin to version 2.6 or later which includes the missing capability check. Alternatively, disable the plugin until an update is available. Review access logs for unauthorized access attempts to the affected endpoint.

Recommended fix High confidence

Version 2.6 or later of the User Registration Using Contact Form 7 plugin

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'User Registration Using Contact Form 7' plugin
  4. If update is available, click 'Update Now' to upgrade to the latest version (2.6 or higher)
  5. Alternatively, manually upload the updated plugin ZIP from wordpress.org/plugins/user-registration-using-contact-form-7
  6. After update, verify the 'get_cf7_form_data' function now includes a capability check (e.g., current_user_can('manage_options'))
  7. Confirm form settings are no longer accessible to unauthenticated users
Caveat Minimal risk - this is a security patch upgrade; review any changelog changes for minor functional differences

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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