Forms For Mailchimp By Optin CatWordPress extension · Fatcatapps
CVE-2023-47545
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. (editor+) Stored Cross-Site Scripting (XSS) vulnerability in Fatcat Apps Forms for Mailchimp by Optin Cat – Grow Your MailChimp List plugin <= 2.5.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 confidenceAuthenticated users with editor+ roles can inject malicious JavaScript through plugin form fields. The payload persists in the database (stored XSS) and executes when administrators or other users view the affected plugin settings or form submissions, allowing session hijacking or privilege escalation.
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
Forms For Mailchimp By Optin CatWordPress extension
<= 2.5.4CVSS 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.
-
Identify plugin installation and versionCheck the installed version of Fatcatapps Forms For Mailchimp By Optin Cat in your WordPress installation. This is typically found in the plugin header, the plugins admin page, or by inspecting the main plugin file for the Version constant.Affected if The installed version is 2.5.4 or lower.
-
Verify presence of editor+ role usersIn WordPress admin, navigate to Users > All Users and review the role assignments. The vulnerability requires an authenticated user with Editor or higher privileges.Affected if You have users assigned the Editor role or any role higher than Editor (such as Administrator).
-
Inspect form submissions for stored XSSAccess the plugin's form submissions data in the WordPress database. Look for entries in the form submission tables that contain script tags, javascript:, onerror, or other XSS payloads in form field values.Affected if Any form submissions contain HTML script tags or JavaScript event handlers in input fields.
-
Check plugin settings for malicious stored contentNavigate to the plugin settings pages in WordPress admin (Forms for Mailchimp > Settings or similar). Inspect all text input fields, labels, and configuration options for unexpected script tags or JavaScript code.Affected if Plugin settings contain unsanitized HTML or JavaScript code, particularly in fields that accept user input from form submissions.
You are affected if the Forms for Mailchimp plugin version is 2.5.4 or lower AND you have users with Editor+ roles with access to create or edit forms, as the vulnerability allows stored XSS injection through form fields.
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 Forms for Mailchimp plugin to a version beyond 2.5.4. If no patched version is available, disable the plugin until a fix is released.
Latest version available in WordPress plugin repository (newer than 2.5.4)
- 1. Check the current version of the 'Forms For Mailchimp By Optin Cat' plugin installed on your WordPress site
- 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
- 3. If the installed version is 2.5.4 or lower, update the plugin to the latest available version
- 4. Verify the update was successful and test the plugin functionality
- 5. Ensure the site is not using any vulnerable version (<=2.5.4)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Forms For Mailchimp By Optin Cat
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47545 — 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-47545 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