dbcve.org
CformsiiWordPress extension · Cformsii Project

CVE-2023-25449

HIGH · 8.8 CVSS v3.1 Published 2023-06-15
Fix available
A fix is available. Upgrade to 15.0.5 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Oliver Seidel, Bastian Germann cformsII plugin <= 15.0.4 versions.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in the cformsII WordPress plugin versions 15.0.4 and below allows remote attackers to induce authenticated administrative users to perform unintended actions by tricking them into submitting malicious requests, potentially leading to configuration changes or data manipulation.

MitigationUpdate cformsII plugin to version 15.0.5 or later which includes anti-CSRF token validation; alternatively, implement and validate anti-CSRF tokens (nonces) on all state-changing form submissions within the plugin.

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
CformsiiWordPress extension
Affected:< 15.0.5

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify cformsII plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'cformsII' in the plugin list
    Affected if cformsII plugin is present and active in the WordPress installation
  2. Check installed cformsII version
    In the Plugins list, find cformsII and view the version number displayed beneath the plugin name, or check the plugin header in /wp-content/plugins/cformsii/cforms.php for the 'Version' tag
    Affected if Version displayed is 15.0.4 or below (any version less than 15.0.5)
  3. Confirm plugin is accessible to administrators
    Verify that the WordPress site has administrator accounts and that cformsII admin functionality is accessible (the CSRF targets authenticated admin users performing configuration actions)
    Affected if Administrators can access cformsII admin interface and site has active admin sessions
  4. Identify state-changing cformsII actions
    Review cformsII admin settings pages for any forms that submit to admin-ajax.php or admin.php with state-changing operations (form submissions, settings saves, database modifications)
    Affected if Any cformsII form submissions or admin configuration actions exist that lack anti-CSRF nonce validation

The environment is affected if the cformsII plugin is installed with a version lower than 15.0.5 and administrators can access cformsII admin functionality that processes state-changing requests without CSRF protection.

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 15.0.5 or later
Fixed in 15.0.5
Interim mitigation

Update cformsII plugin to version 15.0.5 or later which includes anti-CSRF token validation; alternatively, implement and validate anti-CSRF tokens (nonces) on all state-changing form submissions within the plugin.

Recommended fix Moderate confidence

cformsII version 15.0.5

  1. 1. Backup your WordPress database and files before making any changes.
  2. 2. Navigate to the Plugins section in your WordPress admin dashboard.
  3. 3. Locate the cformsII plugin in the installed plugins list.
  4. 4. Check if an update to version 15.0.5 or later is available.
  5. 5. If an update is available, click 'Update Now' to install the fixed version.
  6. 6. After updating, verify the plugin is functioning correctly by testing form submissions.
  7. 7. Confirm the update was successful by checking the plugin version displayed in the Plugins list.

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

Fix this in Cformsii 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 the upgrade done

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-2023-25449 — 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-2023-25449 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