CVE-2025-8145
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 · uneditedThe Redirection for Contact Form 7 plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.2.4 via deserialization of untrusted input in the get_lead_fields function. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain in a Contact Form 7 plugin allows attackers to delete arbitrary files. Additionally, in certain server configurations, Remote Code Execution is possible
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 confidenceThe Redirection for Contact Form 7 plugin for WordPress is vulnerable to PHP Object Injection in the get_lead_fields function, which deserializes untrusted input without proper validation. This allows unauthenticated attackers to inject PHP objects. When combined with a POP chain present in another Contact Form 7 plugin, attackers can delete arbitrary files and potentially achieve remote code execution depending on server configuration.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin is installedCheck if the Redirection for Contact Form 7 plugin exists in your WordPress installation at wp-content/plugins/redirection-for-contact-form-7/ or via the WordPress admin Plugins page.Affected if The plugin is installed and active.
-
Check installed versionView the plugin header in redirection-for-contact-form-7/redirection-for-contact-form-7.php or check the version field in the WordPress admin Plugins list.Affected if The installed version is lower than 3.2.5.
-
Confirm vulnerability trigger point is accessibleThe get_lead_fields function is accessible to unauthenticated users. Check if the plugin endpoint handling this function is exposed (typically via AJAX or direct URL access).Affected if The plugin is active and the vulnerable function endpoint is reachable without authentication.
-
Identify POP chain dependenciesInventory all Contact Form 7 related plugins installed on the WordPress site. Look for other plugins that may contain POP (Property Oriented Programming) chains usable with this injection.Affected if Additional Contact Form 7 plugins with deserialization vulnerabilities or POP chains are present.
Your environment is affected if the Redirection for Contact Form 7 plugin versions below 3.2.5 is installed and active, especially if other Contact Form 7 plugins with deserialization vulnerabilities are also present.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpdate the plugin to version 3.2.5 or later. If an update is unavailable, disable or remove the plugin. Additionally, ensure all Contact Form 7 related plugins are patched and minimize the attack surface by restricting unauthenticated access to plugin endpoints.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-8145 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-8145 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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