MaxbuttonsWordPress extension · Maxfoundry
CVE-2023-36503
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+) Cross-Site Scripting (XSS) vulnerability in Max Foundry WordPress Button Plugin MaxButtons plugin <= 9.5.3 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 cross-site scripting (XSS) vulnerability in MaxButtons WordPress plugin affecting versions 9.5.3 and below. The flaw allows contributor-level or higher authenticated users to inject malicious scripts via plugin parameters.
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
MaxbuttonsWordPress extension
<= 9.5.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.
-
Confirm MaxButtons plugin is installedList the installed plugins in your WordPress environment (typically in wp-content/plugins/) and verify that MaxButtons or MaxButtons Pro by MaxFoundry is present.Affected if MaxButtons plugin is installed and active in WordPress
-
Identify the installed MaxButtons versionAccess the WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the plugin's main header file to locate the version number.Affected if The installed version is 9.5.3 or lower (any version up to and including 9.5.3)
-
Determine the user role requirement for exploitationReview WordPress user roles and capabilities. The vulnerability requires a user with contributor-level or higher permissions (contributor, author, editor, or administrator).Affected if Any user account with contributor-level or higher access exists on the WordPress site
-
Verify plugin parameters are accessible to authenticated usersInspect the MaxButtons plugin settings or button creation interfaces that accept user input. Confirm these endpoints process input without proper sanitization.Affected if The plugin parameters accept and reflect user input without sanitization for authenticated users with contributor+ roles
You are affected if MaxButtons plugin version 9.5.3 or below is installed and your WordPress site has at least one user with contributor-level permissions or higher.
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 dataUpdate MaxButtons plugin to a version greater than 9.5.3, or apply vendor-supplied patch if available. Review user permissions and sanitize user inputs pending remediation.
Fix this in Maxbuttons
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-36503 — 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-36503 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