Wordpress Contact FormsWordPress extension · Cimatti
CVE-2023-35051
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 · uneditedMissing Authorization vulnerability in Cimatti Consulting Contact Forms by Cimatti allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Contact Forms by Cimatti: from n/a through 1.5.7.
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 confidenceMissing authorization vulnerability in the Contact Forms by Cimatti WordPress plugin (versions through 1.5.7) allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to administrative functions or sensitive data due to missing capability checks or improper privilege validation.
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
< 1.5.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationNavigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and look for 'Contact Forms by Cimatti' or search for it in the plugin directory.Affected if The plugin is installed and active in WordPress.
-
Identify installed versionIn the plugins list, click on the plugin to view details, or check the plugin's main PHP file (usually in wp-content/plugins/contact-forms-by-cimatti/) for a version constant or header. Alternatively, check the readme.txt file in the plugin directory for the 'Stable tag' entry.Affected if The installed version is 1.5.7 or earlier (any version below 1.5.8).
-
Verify plugin is activeIn WordPress admin > Plugins, confirm the plugin status shows as 'Active'. Only active plugins expose their functionality to potential exploitation.Affected if The plugin is actively installed and enabled on the WordPress site.
-
Check for exposed admin endpointsInspect the plugin's main PHP file for registered WordPress ajax actions (wp_ajax_*) or admin menu pages. Look for functions that perform sensitive operations without current_user_can() checks or capability validation.Affected if The plugin registers ajax handlers or admin pages that perform privileged operations without proper authorization checks.
If the Contact Forms by Cimatti plugin is installed, active, and running version 1.5.7 or below, the site is affected by this missing authorization vulnerability.
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 · scoped1.5.8
Update to the latest version of Contact Forms by Cimatti plugin which should include proper authorization checks, capability verification, and nonce validation for all privileged operations.
Contact Forms by Cimatti version 1.5.8
- Backup your WordPress database and files before making any changes
- Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- Locate the 'Contact Forms by Cimatti' (or 'Cimatti Consulting Contact Forms') plugin
- Click 'Update now' or manually update to version 1.5.8
- Verify the plugin version shows 1.5.8 after updating
- Test contact form submissions to ensure functionality works correctly
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
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35051 — 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-2023-35051 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