Stored XSS via undisclosed content handling
Published Feb 16, 2025 · Updated Apr 28, 2026
Stored XSS in Themeum Qubely 1.8.12 and earlier allows remote authenticated users to execute scripts in visitors' browsers. Patchstack has not disclosed the affected function, field, or missing encoding operation that permits stored script content. Contributor-level access is required to store the payload, and exploitation occurs only when another user views the affected content, exposing that user's browser session to attacker-controlled script actions.
Summary
What happened
Stored XSS in Themeum Qubely 1.8.12 and earlier allows remote authenticated users to execute scripts in visitors' browsers. Patchstack has not disclosed the affected function, field, or missing encoding operation that permits stored script content. Contributor-level access is required to store the payload, and exploitation occurs only when another user views the affected content, exposing that user's browser session to attacker-controlled script actions.
The record
- CVE
- CVE-2025-26767
- Published
- Feb 16, 2025
- Updated
- Apr 28, 2026
- Vendor
- Themeum
- Product
- Qubely
- Classifications
- CWE-79, CAPEC-592, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 16, 2025CVE publishedPublication date reported by the CVE source.
- Apr 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=0 <=1.8.12 changes=[{"at":"1.8.13","status":"unaffected"}]
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