CVE-2026-6835 — Cross-Site Scripting (XSS)
CVE-2026-6835 — The a+HCM developed by aEnrich has an Arbitrary File Upload vulnerability, allowing unauthenticated remote attackers to upload arbitrary files to any path, including HTML documents, which may result in a XSS-like effect.
What This Means For You
- If your environment is affected by CWE-434, review your exposure and prioritize patching based on your environment. Monitor vendor advisories for CVE-2026-6835 updates and patches.
Related ATT&CK Techniques
🛡️ Detection Rules
3 rules · 6 SIEM formats3 detection rules auto-generated for this incident, mapped to MITRE ATT&CK. Sigma YAML is free — export to any SIEM format via the Intel Bot.
CVE-2026-6835 - a+HCM Arbitrary File Upload leading to XSS
Indicators of Compromise
| ID | Type | Indicator |
|---|---|---|
| CVE-2026-6835 | vulnerability | CVE-2026-6835 |
| CWE-434 | weakness | CWE-434 |
Written by SCW Vulnerability Desk
Source & Attribution
| Source Platform | NVD |
| Channel | National Vulnerability Database |
| Published | April 22, 2026 at 07:16 UTC |
This content was curated and summarized by Shimi's Cyber World for informational purposes. It is not copied or republished in full. All intellectual property rights remain with the original author and source.
Believe this infringes your rights? Submit a takedown request.
Related Posts
Spring Security Authorization Bypass: High Severity Vulnerability
CVE-2026-22754 — Vulnerability in Spring Spring Security. If an application uses to define the servlet path for computing a path matcher, then the servlet path is...
Spring Security Flaw Bypasses Auth, Authorization
CVE-2026-22753 — Vulnerability in Spring Spring Security. If an application is using securityMatchers(String) and a PathPatternRequestMatcher.Builder bean to prepend a servlet path, matching requests to that filter chain may...
CVE-2026-22748 — Spring Security: From Vulnerability
CVE-2026-22748 — Vulnerability in Spring Spring Security. When an application configures JWT decoding with NimbusJwtDecoder or NimbusReactiveJwtDecoder, it must configure an OAuth2TokenValidator separately, for example by calling setJwtValidator.This issue affects...