dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-12250

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-18
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 Accept Authorize.NET Payments Using Contact Form 7 plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 2.2 via the cf7adn-info.php file. This makes it possible for unauthenticated attackers to extract configuration data which can be used to aid in other attacks.

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 Accept Authorize.NET Payments Using Contact Form 7 plugin for WordPress is vulnerable to information exposure in the cf7adn-info.php file. Unauthenticated attackers can extract sensitive configuration data (likely including API credentials or payment settings) which can be leveraged for further attacks.

MitigationUpdate the plugin to the latest version beyond 2.2 to remediate this vulnerability. Also review and rotate any exposed credentials as a precaution.

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. Confirm plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Accept Authorize.NET Payments Using Contact Form 7' or 'cf7adn' in the plugin list. Note the installed version displayed.
    Affected if Plugin is not installed or has been removed entirely
  2. Identify installed plugin version
    In WordPress admin > Plugins, find the plugin and note the version number displayed under the plugin name. Alternatively, inspect the plugin's main PHP file header or readme.txt for the Version field.
    Affected if Version is 2.2 or lower (including any 2.x version below 2.2)
  3. Locate the vulnerable file
    Check if the file cf7adn-info.php exists in the plugin directory. Common path: wp-content/plugins/authorize-net-cf7-addon/cf7adn-info.php or similar. Use FTP, file manager, or WP CLI: find wp-content/plugins -name 'cf7adn-info.php'
    Affected if The file cf7adn-info.php exists in the plugin directory
  4. Test file accessibility
    Attempt to access the file directly via web browser: visit https://yourdomain.com/wp-content/plugins/[plugin-folder]/cf7adn-info.php. If it loads and displays configuration data, API keys, or settings without authentication, the vulnerability is exposed.
    Affected if The file is web-accessible and returns sensitive configuration data without requiring login

User is affected if the plugin version is 2.2 or lower AND the cf7adn-info.php file exists and is accessible without authentication, allowing unauthenticated extraction of sensitive payment 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 the latest version beyond 2.2 to remediate this vulnerability. Also review and rotate any exposed credentials as a precaution.

Recommended fix Moderate confidence

version 2.3 or later (latest available version)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Accept Authorize.NET Payments Using Contact Form 7'
  4. If an update is available, click 'Update Now' to upgrade to the latest version
  5. Alternatively, manually download the updated plugin from wordpress.org/plugins and upload it via Plugins > Add New > Upload Plugin
  6. After updating, verify the cf7adn-info.php file has been removed or secured

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-2024-12250 — 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-2024-12250 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