CVE-2025-26529 | Stored XSS risk in admin live log

Description information displayed in the site administration live log required additional sanitizing to prevent a stored XSS risk.

Published: 2025-02-24 Last update: 2025-08-08 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-26529 is rated Moderate Risk (60.3/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.95%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-26529

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-03 0.59% 0.95% +0.36%
2 2026-03-29 0.15% 0.59% +0.44%
3 2026-01-18 — 0.15% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-26529

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.3 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.6 6.0 [email protected]
6.1 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 2.7 [email protected]

Weakness enumeration for CVE-2025-26529

GitHub Security Advisory for CVE-2025-26529

GHSA-wr88-x8cm-7cgq · Severity: high · Ecosystem: composer — Moodle has a stored XSS risk in admin live log

OS Trackers for CVE-2025-26529

vendor priority summary link
ubuntu medium CVE-2025-26529 medium priority: Ubuntu including 1 source packages (moodle), 9 status rows across 9 suites (bionic, focal, jammy, noble, oracular, plucky, questing, upstream, xenial): DNE 6, needs-triage 3. https://ubuntu.com/security/CVE-2025-26529

Affected software / configurations for CVE-2025-26529

Vendor Product Version Raw CPE
moodle moodle >= 4.1.0, < 4.1.16 cpe:2.3:a:moodle:moodle:*:*:*:*:*:*:*:*
moodle moodle >= 4.3.0, < 4.3.10 cpe:2.3:a:moodle:moodle:*:*:*:*:*:*:*:*
moodle moodle >= 4.4.0, < 4.4.6 cpe:2.3:a:moodle:moodle:*:*:*:*:*:*:*:*
moodle moodle >= 4.5.0, < 4.5.2 cpe:2.3:a:moodle:moodle:*:*:*:*:*:*:*:*

References for CVE-2025-26529

cvelogic Threat Intelligence