dbcve.org
Wordpress Contact FormsWordPress extension · Cimatti

CVE-2023-47230

HIGH · 8.8 CVSS v3.1 Published 2023-11-13
Fix available
A fix is available. Upgrade to after 1.6.0 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 Cimatti Consulting WordPress Contact Forms by Cimatti plugin <= 1.6.0 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 Cimatti Consulting WordPress Contact Forms plugin versions 1.6.0 and earlier allows attackers to potentially trick authenticated administrators into performing unintended actions such as modifying form settings, deleting entries, or submitting forms on behalf of the user.

MitigationUpdate the plugin to a version newer than 1.6.0 which should include proper anti-CSRF token validation; alternatively, implement WordPress nonces on all form submissions and state-changing operations.

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
Wordpress Contact FormsWordPress extension
Affected:<= 1.6.0

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. Locate the plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'cimatti-wordpress-contact-forms' or similar naming pattern; alternatively, view installed plugins in WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists in the WordPress installation
  2. Identify the installed version
    In WordPress admin, find the plugin in the plugins list and read the version number from the 'Version' column; or open the main plugin PHP file and look for the 'Version' header in the plugin comments
    Affected if The reported version is 1.6.0 or lower
  3. Verify the plugin is active
    Check if the plugin is enabled in WordPress admin under Plugins > Installed Plugins - look for a 'Active' status indicator next to the plugin name
    Affected if The plugin shows as Active and the version is 1.6.0 or earlier
  4. Confirm vulnerability scope
    The CSRF flaw affects any authenticated administrator using the plugin; no specific configuration toggle exists - the vulnerability is inherent to the lack of nonce validation in form handling code
    Affected if You are using version 1.6.0 or earlier with the plugin active on a WordPress site where administrators can be tricked into visiting malicious pages while logged in

You are affected if the Cimatti Consulting WordPress Contact Forms plugin version 1.6.0 or earlier is installed and active on your WordPress site, as the plugin lacks anti-CSRF token validation on form submissions.

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.6.0
Interim mitigation

Update the plugin to a version newer than 1.6.0 which should include proper anti-CSRF token validation; alternatively, implement WordPress nonces on all form submissions and state-changing operations.

Recommended fix Moderate confidence

Latest version available in the WordPress plugin repository (later than 1.6.0)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Cimatti Consulting WordPress Contact Forms' plugin
  4. Click 'Update now' if an update is available, or manually download the latest version from the WordPress plugin repository and upload it
  5. Verify the update was successful by checking the plugin version

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

Fix this in Wordpress Contact Forms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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