Rendered note modification via stored script injection
Published Dec 19, 2022 · Updated Apr 14, 2025
Stored XSS in Alagrede Znote before 1.7.11 allows local users to inject script that changes rendered note content. Public records do not identify the affected renderer or the input path that stores unneutralized markup, and the referenced commit changes only example content. Reaching the flaw requires local high-privilege access and a user action; reported impact is limited to modifying displayed content.
Summary
What happened
Stored XSS in Alagrede Znote before 1.7.11 allows local users to inject script that changes rendered note content. Public records do not identify the affected renderer or the input path that stores unneutralized markup, and the referenced commit changes only example content. Reaching the flaw requires local high-privilege access and a user action; reported impact is limited to modifying displayed content.
The record
- CVE
- CVE-2022-4614
- Published
- Dec 19, 2022
- Updated
- Apr 14, 2025
- Vendor
- Alagrede
- Product
- Znote
- Classifications
- CWE-79
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 19, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 2025Record 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=unspecified <1.7.11
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
- huntr.dev bounty proof of conceptproof of concept · unverified
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