On this page
CWE-87: Improper Neutralization of Alternate XSS Syntax
Weakness Summary
The product does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.
- Canonical source: MITRE CWE-87 (opens in a new tab)
- Published Atomicorp CVE observations: 11
- Distinct affected products in those observations: 7
- Active Atomicorp rules associated with this weakness: 15
Atomicorp Research Context
Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.
The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.
A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.
Selected Published CVE Observations
| CVE | Vulnerability | Product | Atomicorp finding | Observed rules |
|---|---|---|---|---|
| CVE-2026-55237 | AutoGPT SignUp Page has DOM-Based XSS and Open Redirect | AutoGPT | Protected by Atomicorp rules | 333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341256 , 341266 , 342259 , 346755 |
| CVE-2026-35534 | ChurchCRM has Stored XSS in PersonView.php via Facebook Field Attribute Injection | churchcrm | Protected by Atomicorp rules | 333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341256 , 341266 , 342259 , 346755 , 350147 , 350148 |
| CVE-2026-34598 | YesWiki has Persistant Blind XSS at "/?BazaR&vue=consulter" | yeswiki | Protected by Atomicorp rules | 333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341256 , 341266 , 342259 , 346755 , 350147 , 350148 |
| CVE-2023-35156 | XWiki >= 6.0-rc-1 - Cross-Site Scripting | xwiki | Protected by Atomicorp rules | 346755 , 350148 |
| CVE-2023-35158 | XWiki - Cross-Site Scripting | xwiki | Protected by Atomicorp rules | 346755 , 350148 |
| CVE-2023-35159 | XWiki >= 3.4-milestone-1 - Cross-Site Scripting | xwiki | Protected by Atomicorp rules | 346755 , 350148 |
| CVE-2023-35160 | XWiki >= 2.5-milestone-2 - Cross-Site Scripting | xwiki | Protected by Atomicorp rules | 346755 , 350148 |
| CVE-2023-35161 | XWiki >= 6.2-milestone-1 - Cross-Site Scripting | xwiki | Protected by Atomicorp rules | 346755 , 350148 |
| CVE-2026-42458 | Magento LTS: Reflected XSS - Import -> Data Flow (profiles) | magento-lts | Protected by Atomicorp rules | 333140 , 333141 , 340087 , 340095 , 340099 , 340147 , 340148 , 341099 , 341266 , 342259 , 346755 , 350147 , 350148 |
| CVE-2025-62414 | bagisto - Cross Site Scripting (XSS) in Create New Customer | bagisto | Protected by Atomicorp rules | 333140 , 333141 , 340095 , 340147 , 340148 , 342259 , 346755 , 350147 , 350148 |
| CVE-2026-85293 | InvoicePlane: Stored Cross-Site Scripting (XSS) via Client Email in Invoice and Quote Mailer Forms | InvoicePlane | Protected by Atomicorp rules | 333140 , 333141 , 340095 , 340099 , 340147 , 340148 , 340149 , 341099 , 341256 , 341266 , 342259 , 346755 , 350147 , 350148 |
Associated Atomicorp WAF Rules
| Rule | Status | Behavior |
|---|---|---|
| 333140 | Active | disruptive (deny) |
| 333141 | Active | disruptive (deny) |
| 340087 | Active | disruptive (deny) |
| 340095 | Active | disruptive (deny) |
| 340099 | Active | disruptive (deny) |
| 340147 | Active | disruptive (deny) |
| 340148 | Active | disruptive (deny) |
| 340149 | Active | disruptive (deny) |
| 341099 | Active | disruptive (deny) |
| 341256 | Active | disruptive (deny) |
| 341266 | Active | disruptive (deny) |
| 342259 | Active | disruptive (deny) |
| 346755 | Active | disruptive (deny) |
| 350147 | Active | disruptive (deny) |
| 350148 | Active | disruptive (deny) |
Related MITRE CAPEC Context
MITRE associates this CWE with the following attack-pattern entries. These taxonomy relationships are context, not Atomicorp coverage claims: