CVE-2026-40229: Helpy contains a stored cross-site scripting vulnerability in the post author display logic
Source GCVE Database
Not known to be exploited · CVSS 5.1 Medium.
Data as of 27 Oct 2026, 00:38 UTC
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| helpyiohelpy | Affected
| Fixed in– |
GitHubhelpyio/helpypkg:github/helpyio/helpyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability is in version 2.8.0, users should monitor for vendor advisories for a fix. Until then, consider restricting account name input or sanitizing output in affected contexts as a temporary mitigation.
Description
Helpy version 2.8.0 contains a stored cross-site scripting (XSS) vulnerability in the post author display logic. Registered users can inject arbitrary HTML into their account name, which is then rendered unescaped in public forum threads, the admin ticket view, and HTML notification emails. This could lead to partial compromise of confidentiality and integrity but does not affect availability.