VU#699627: Readwise Reader for Android, version 8.7.2, contains multiple XSS vulnerabilities
Source CERT/CC
Mentioned vulnerabilities
Not known to be exploited · CVSS 6.1 Medium.
Data as of 13 Nov 2026, 23:53 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 25 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 14 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ReadwiseReader | Affected
| Fixed in– |
AI-suggested
Users should update Readwise Reader for Android to version 8.10.1 or later, which includes a patch addressing the sanitizer wildcard issue (CVE-2026-18320). Since the vendor could not be reached for coordinated disclosure, users should monitor for further vendor updates that address all identified vulnerabilities. Additionally, users should exercise caution when adding content from untrusted sources and manually review document metadata before saving articles to reduce exposure to malicious content.
Description
Readwise Reader for Android version 8.7.2 contains three stored cross-site scripting (XSS) vulnerabilities. These flaws allow attackers who can supply malicious documents or metadata to execute arbitrary JavaScript within the app's WebView context. The vulnerabilities arise from insufficient sanitization of document metadata fields, improper escaping of URL metadata, and permissive sanitization rules for SVG markup. Exploitation could compromise user data confidentiality and integrity, including access to stored documents, credentials, and session tokens. A patch addressing one of the issues is available in version 8.10.1. Users are advised to update when possible and exercise caution when adding content from untrusted sources.