CVE-2025-60506: Moodle PDF Annotator plugin · Cross-site Scripting
Source CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 26 Oct 2026, 17:16 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:L/UI:R/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
AI-suggested
Organizations should immediately audit their Moodle installations to identify the use of the PDF Annotator plugin version 1.5 release 9. Until an official patch is released, administrators should consider disabling the Public Comments feature or restricting commenting privileges to trusted users only. Implementing strict input validation and output encoding on comment fields can reduce the risk of XSS payload injection. Additionally, deploying Content Security Policy (CSP) headers can help mitigate the impact of injected scripts by restricting script execution sources. Regular user education on phishing and suspicious content, combined with monitoring for unusual session activity, can help detect exploitation attempts. Finally, organizations should stay alert for official patches or updates from the plugin maintainers and apply them promptly once available.
Description
Moodle PDF Annotator plugin v1.5 release 9 allows stored cross-site scripting (XSS) via the Public Comments feature. An attacker with a low-privileged account (e.g., Student) can inject arbitrary JavaScript payloads into a comment. When any other user (Student, Teacher, or Admin) views the annotated PDF, the payload is executed in their browser, leading to session hijacking, credential theft, or other attacker-controlled actions.