dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-13717

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 Contact Form vCard Generator plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'wp_gvccf_check_download_request' function in all versions up to, and including, 2.4. This makes it possible for unauthenticated attackers to export sensitive Contact Form 7 submission data via the 'wp-gvc-cf-download-id' parameter, including names, phone numbers, email addresses, and messages.

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

This is a broken access control vulnerability in the Contact Form vCard Generator WordPress plugin. The 'wp_gvccf_check_download_request' AJAX function lacks a capability check, allowing any unauthenticated user to export sensitive Contact Form 7 form submissions by manipulating the 'wp-gvc-cf-download-id' parameter. This exposes personal data including names, phone numbers, email addresses, and message contents.

MitigationUpdate to version 2.5 or later which includes proper authorization checks. Until a patch is available, consider disabling the plugin or restricting access to the vulnerable endpoint at the web server level.

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 Contact Form vCard Generator plugin is installed
    Log in to WordPress admin, go to Plugins > Installed Plugins, and look for 'Contact Form vCard Generator' or 'wp_gvccf' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to 'contact-form-vcard-generator' or containing 'gvccf'.
    Affected if The plugin appears in the WordPress plugins list.
  2. Determine installed plugin version
    In WordPress admin Plugins page, click 'View Details' on the Contact Form vCard Generator plugin to see the version number. Alternatively, open the main plugin PHP file (usually named plugin-name.php in the plugin folder) and look for the 'Version' header in the plugin comment block.
    Affected if The version is lower than 2.5, or the version cannot be determined (indicating an outdated release).
  3. Confirm Contact Form 7 is also installed
    In WordPress admin, go to Plugins > Installed Plugins and verify 'Contact Form 7' is installed and active. The vulnerability specifically targets CF7 form submissions.
    Affected if Contact Form 7 is installed and active alongside the vulnerable vCard Generator plugin.
  4. Test unauthenticated AJAX endpoint accessibility
    Send a POST request to /wp-admin/admin-ajax.php with action=wp_gvccf_check_download_request and a parameter wp-gvc-cf-download-id set to any numeric value (e.g., 1). Use a tool like curl: curl -X POST http://YOURSITE/wp-admin/admin-ajax.php -d 'action=wp_gvccf_check_download_request&wp-gvc-cf-download-id=1'
    Affected if The server returns a response without requiring authentication (no 401/403 error), indicating the endpoint is exposed.

If the Contact Form vCard Generator plugin version is below 2.5 AND Contact Form 7 is active AND the AJAX endpoint responds to unauthenticated requests, the environment is affected by this vulnerability.

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 2.5 or later which includes proper authorization checks. Until a patch is available, consider disabling the plugin or restricting access to the vulnerable endpoint at the web server level.

Recommended fix High confidence

Contact Form vCard Generator version 2.5

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Contact Form vCard Generator' plugin
  4. Click 'Update Now' if an update is available, or manually upload version 2.5 of the plugin
  5. Verify the plugin version shows 2.5 after updating
  6. Test that the download functionality still works for authorized users

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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