Contact Form Entries Contact Form 7 Wpforms And MoreWordPress extension · Crmperks
CVE-2023-33311
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 · uneditedAuth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in CRM Perks Contact Form Entries plugin <= 1.3.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 · high confidenceAuthenticated contributor+ users can inject malicious JavaScript via form submission fields in the CRM Perks Contact Form Entries plugin. The injected script is stored in the database and executes when admin users view the contact form entries, achieving stored XSS.
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
Contact Form Entries Contact Form 7 Wpforms And MoreWordPress extension
<= 1.3.0CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 CRM Perks Contact Form Entries plugin is installedNavigate to WordPress admin > Plugins and look for 'Crmperks Contact Form Entries' or 'Contact Form 7 Wpforms And More', or run: wp plugin list --name='*crm*'Affected if Plugin is installed and active
-
Check installed plugin versionIn Plugins list, click 'View Details' on the CRM Perks plugin, or inspect the main plugin file header in wp-content/plugins/crm-perks-contact-form-entries/Affected if Version number is 1.3.0 or lower
-
Confirm contributor+ role access existsReview user roles in WordPress admin > Users > Roles, or check if any users with contributor, author, or editor roles exist who can access the plugin's form submission functionalityAffected if Users with contributor or higher roles exist and can submit forms through the plugin
-
Inspect database for suspicious script content in form entriesQuery the plugin's form entry database table (commonly wp_cf7_cl_entry or similar, check plugin documentation for exact table name) for entries containing <script, javascript:, onload, onerror, or other HTML/script tags in submission fieldsAffected if Form entry records contain unsanitized HTML or script tags in submission data
-
Check if admin users view form entriesLog in as administrator and navigate to the plugin's form entries list page where admin users review submitted contact form dataAffected if Admin users access the form entries viewing interface
User is affected if the CRM Perks Contact Form Entries plugin version is 1.3.0 or lower, contributor or higher role users can submit forms, and unsanitized script content exists in the database form entries that would execute when admins view them.
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 dataUpgrade to plugin version >1.3.0 which includes proper input sanitization and output escaping. Until then, restrict contributor+ role permissions and monitor for suspicious form submissions.
Fix this in Contact Form Entries Contact Form 7 Wpforms And More
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33311 — 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-33311 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