MaxButtons < 9.8.1 - Admin+ Stored XSS via Text Color
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: Unknown WordPress Button Plugin MaxButtons 9.8.1.
Low priority for now. Upgrade to Unknown WordPress Button Plugin MaxButtons 9.8.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The WordPress Button Plugin MaxButtons WordPress plugin before 9.8.1 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup).
- Published
- Dec 20, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 35th percentile
- CWE
- CWE-79
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Is MaxButtons – Create buttons on your site?
WP Lens reads your site's plugin, theme and WordPress versions from the outside and matches them to known vulnerabilities. Works without an account.
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| maxfoundry | maxbuttons | cpe:2.3:a:maxfoundry:maxbuttons |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- maxfoundry maxbuttonsbefore 9.8.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (WPScan). Independent of NVD's CPE analysis and usually ahead of it.
Unknown WordPress Button Plugin MaxButtons
- before 9.8.1affected · semver
Same product
maxfoundry: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-36346WordPress MaxButtons plugin <= 9.2 - Multiple Cross-Site Request Forgery (CSRF) vulnerabilities35Monitor
- CVE-2014-125092MaxButtons Plugin maxbuttons-button.php maxbuttons_strip_px cross site scripting24Monitor
- CVE-2025-39444WordPress MaxButtons plugin <= 9.8.3 - Cross Site Scripting (XSS) vulnerability23Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-3026Jul 13, 2024 · WordPress Button Plugin MaxButtons < 9.7.8 - Editor+ Stored XSS21Monitor
- ← EarlierCVE-2024-6499Aug 24, 2024 · WordPress Button Plugin MaxButtons <= 9.7.8 - Full Path Disclosure21Monitor
- ← EarlierCVE-2024-10555Dec 20, 2024 · MaxButtons < 9.8.1 - Admin+ Stored XSS via Button Width19Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Unknown WordPress Button Plugin MaxButtons | 9.8.1 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Dmitrii Ignatyevfinder
- WPScancoordinator
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-39444118 days apartWordPress MaxButtons plugin <= 9.8.3 - Cross Site Scripting (XSS) vulnerability23Monitor
- CVE-2024-3026160 days apartWordPress Button Plugin MaxButtons < 9.7.8 - Editor+ Stored XSS21Monitor
- CVE-2023-7029319 days apartWordPress Button Plugin MaxButtons <= 9.7.6 - Authenticated(Contributor+) Stored Cross-Site Scripting via shortcode21Monitor
- CVE-2023-36503514 days apartWordPress MaxButtons Plugin <= 9.5.3 is vulnerable to Cross Site Scripting (XSS)21Monitor
- CVE-2024-105550 days apartMaxButtons < 9.8.1 - Admin+ Stored XSS via Button Width19Monitor
- CVE-2023-6594347 days apartWordPress Button Plugin MaxButtons <= 9.7.4 - Authenticated (Administrator+) Stored Cross-Site Scripting19Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
nvd-secondary
Root cause
User content is inserted into the page as HTML. The browser interprets the content as code rather than data.
The bug in code
The whole CWE-79 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
commentEl.innerHTML = comment.body;Fixed
commentEl.textContent = comment.body;Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →