Stored XSS via unescaped repo shortcode attribute
Published May 27, 2026 · Updated May 27, 2026
Stored XSS in octalmage GitHub Shortcode 0.1 and earlier allows remote authenticated users to inject scripts through the repo attribute. The github shortcode callback inserts the attacker-controlled repo value into generated page markup without sanitizing the input or escaping the output. Contributor-level access is required to save the payload; the script runs in visitors' browsers whenever they open the affected page.
Summary
What happened
Stored XSS in octalmage GitHub Shortcode 0.1 and earlier allows remote authenticated users to inject scripts through the repo attribute. The github shortcode callback inserts the attacker-controlled repo value into generated page markup without sanitizing the input or escaping the output. Contributor-level access is required to save the payload; the script runs in visitors' browsers whenever they open the affected page.
The record
- CVE
- CVE-2026-8042
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- octalmage
- Product
- GitHub Shortcode
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo