Stored script execution via unencoded index names
Published Jan 28, 2026 · Updated Jan 28, 2026
Stored cross-site scripting in RethinkDB 2.4.0 through 2.4.3 allows remote authenticated users to execute script in an administrator's browser. The web administration UI inserts an attacker-controlled secondary-index name into the deletion interface without HTML encoding, so repeated delete actions interpret the name as markup. Exploitation requires administrative access to create the crafted index and user interaction in the web UI; successful exploitation alters browser-rendered content without affecting server confidentiality or availability.
Summary
What happened
Stored cross-site scripting in RethinkDB 2.4.0 through 2.4.3 allows remote authenticated users to execute script in an administrator's browser. The web administration UI inserts an attacker-controlled secondary-index name into the deletion interface without HTML encoding, so repeated delete actions interpret the name as markup. Exploitation requires administrative access to create the crafted index and user interaction in the web UI; successful exploitation alters browser-rendered content without affecting server confidentiality or availability.
The record
- CVE
- CVE-2026-1520
- Published
- Jan 28, 2026
- Updated
- Jan 28, 2026
- Vendor
- RethinkDB
- Product
- RethinkDB
- Classifications
- CWE-94, CWE-79, T1203
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jan 28, 2026CVE publishedPublication date reported by the CVE source.
- Jan 28, 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=2.4.0
- Affected versionversion=2.4.1
- Affected versionversion=2.4.2
- Affected versionversion=2.4.3
What conditions does exploitation require?
What is affected?
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
- Secondary-index name stored XSS proof of conceptproof of concept · demonstrated
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