dbcve.org
Contact Form 7 Email Add OnWordPress extension · Krishaweb

CVE-2024-10898

HIGH · 8.8 CVSS v3.1 Published 2024-11-21
Fix available
A fix is available. Upgrade to after 1.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 7 Email Add on plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.9 via the cf7_email_add_on_add_admin_template() function. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary PHP files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where php files can be uploaded and included.

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 Contact Form 7 Email Add on WordPress plugin is vulnerable to Local File Inclusion via the cf7_email_add_on_add_admin_template() function. Authenticated attackers with Contributor-level access can include and execute arbitrary PHP files already present on the server, enabling code execution and potential bypass of access controls.

MitigationUpdate the plugin to a version beyond 1.9 when available, or implement strict input validation and sanitization on file path parameters in the cf7_email_add_on_add_admin_template() function to prevent path traversal attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Contact Form 7 Email Add OnWordPress extension
Affected:<= 1.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 7 Email Add On plugin is installed
    Navigate to Plugins > Installed Plugins in WordPress admin, or inspect the /wp-content/plugins/ directory for a folder containing 'cf7' and 'email' in the name.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Check the installed plugin version
    In WordPress admin, view the plugin details to see the version number, or open the main plugin PHP file and check the 'Version' header in the plugin comment block.
    Affected if The version is 1.9 or lower.
  3. Confirm the vulnerable function exists in the codebase
    Inspect the main plugin PHP file(s) and search for the function 'cf7_email_add_on_add_admin_template' - this function handles template inclusion and is where the LFI vulnerability resides.
    Affected if The function cf7_email_add_on_add_admin_template is present in the plugin code.
  4. Identify users with Contributor-level or higher access
    In WordPress admin, go to Users > All Users and review the role column. Check for any users assigned the Contributor, Author, Editor, or Administrator roles.
    Affected if There are one or more users with Contributor-level or higher access.

A user is affected if the plugin version is 1.9 or lower AND the plugin is installed AND there exists at least one user with Contributor-level or higher access who could trigger the LFI 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
Upgrade available Upgrade to a release after 1.9
Interim mitigation

Update the plugin to a version beyond 1.9 when available, or implement strict input validation and sanitization on file path parameters in the cf7_email_add_on_add_admin_template() function to prevent path traversal attacks.

Recommended fix Moderate confidence

Any version greater than 1.9 (check WordPress plugin repository for latest stable release)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Contact Form 7 Email Add On' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  5. After updating, verify the plugin version is greater than 1.9

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

Fix this in Contact Form 7 Email Add On Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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