CVE-2025-47491
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in A WP Life Contact Form Widget new-contact-form-widget allows Cross Site Request Forgery.This issue affects Contact Form Widget: from n/a through <= 1.4.6.
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 · moderate confidenceCross-Site Request Forgery (CSRF) vulnerability in the A WP Life Contact Form Widget WordPress plugin (new-contact-form-widget) allows remote attackers to perform unauthorized actions on behalf of authenticated administrators by tricking them into submitting malicious requests. The vulnerability affects all versions up to and including 1.4.6, rated at CVSS 7.4 (HIGH).
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation statusLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'A WP Life Contact Form Widget' or 'new-contact-form-widget' in the list of installed plugins.Affected if The plugin is not found in the installed plugins list, then the environment is not affected.
-
Locate the plugin version numberIn the WordPress Plugins admin page, click on the plugin name or look for the version number displayed in the plugin description row. Alternatively, access the plugin's main PHP file (typically at wp-content/plugins/new-contact-form-widget/*.php) and check the plugin header for the 'Version' field.Affected if Unable to determine the version indicates potential unaudited installation.
-
Compare installed version against vulnerable rangeIf the plugin is installed, compare the identified version number to the affected range: all versions up to and including 1.4.6. For example, if version 1.4.6 is installed, it is within the affected range.Affected if The installed version is 1.4.6 or lower, indicating the environment is affected by this CSRF vulnerability.
The environment is affected if the A WP Life Contact Form Widget plugin (new-contact-form-widget) is installed with version 1.4.6 or any earlier version.
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.
dbcve · scopedUpdate the plugin to the latest version once the patch is released. In the interim, ensure WordPress nonces are implemented on all form submissions and AJAX actions within the plugin, and warn administrators against clicking untrusted links while logged in.
Latest available version of Contact Form Widget (vendor should have released version > 1.4.6 with CSRF fix)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate 'Contact Form Widget' by A WP Life
- 4. Check the current version installed (should be <= 1.4.6)
- 5. If an update is available, click 'Update Now' to upgrade to the latest version
- 6. Verify the update completed successfully
- 7. Test the contact form functionality to ensure it works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47491 — 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-47491 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