Code Snippets ExtensionWordPress extension · Mainwp
CVE-2023-23650
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. (subscriber+) Stored Cross-Site Scripting (XSS) vulnerability in MainWP MainWP Code Snippets Extension plugin <= 4.0.2 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 confidenceStored Cross-Site Scripting (XSS) vulnerability in MainWP Code Snippets Extension allows authenticated users with subscriber+ role to inject malicious JavaScript that persists and executes when other users view the affected content in the WordPress admin dashboard.
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
Code Snippets ExtensionWordPress extension
< 4.0.3CVSS 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.
-
Check installed version of MainWP Code Snippets ExtensionNavigate to Plugins > Installed Plugins in WordPress admin, find 'MainWP Code Snippets Extension', and view the version number displayed thereAffected if Version is lower than 4.0.3
-
Confirm the extension is activeGo to Plugins > Installed Plugins and verify that MainWP Code Snippets Extension is activatedAffected if The extension is active and version is below 4.0.3
-
Access the Code Snippets settings pageNavigate to MainWP > Extensions > Code Snippets or the equivalent menu path where code snippets are managed in the WordPress admin dashboardAffected if You can access the code snippets management interface with a subscriber+ role account
-
Review existing code snippets for suspicious contentExamine each code snippet listed in the extension for any JavaScript tags, event handlers, or script-like content that was not intentionally added by an administratorAffected if Any code snippet contains untrusted or malicious JavaScript code that could execute in other users' browsers
You are affected if the MainWP Code Snippets Extension version is below 4.0.3 and the extension is active, particularly if untrusted subscriber+ users can access or create code snippets that may contain malicious scripts.
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 · scoped4.0.3
Update MainWP Code Snippets Extension to version greater than 4.0.2 to patch the vulnerability, or disable the plugin until the fix is available.
4.0.3
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find the MainWP Code Snippets Extension plugin
- Check if the current version is below 4.0.3
- If update available, click 'Update Now' to upgrade to version 4.0.3 or later
- Alternatively, download the latest version from the WordPress plugin repository or your MainWP account and reinstall
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Code Snippets Extension
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-23650 — 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-23650 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