CVE-2025-26531 | IDOR in badges allows disabling of arbitrary badges

Insufficient capability checks made it possible to disable badges a user does not have permission to access.

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

CVE-2025-26531 is rated Low Risk (32.4/100): CVSS Low severity, with medium exploitation likelihood (EPSS 0.34%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-26531

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-05 0.36% 0.34% -0.01%
2 2026-04-04 0.32% 0.36% +0.04%
3 2026-03-29 — 0.32% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.1 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/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: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:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
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.
 1.6 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
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.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2025-26531

GitHub Security Advisory for CVE-2025-26531

GHSA-g88w-v4cq-qgcp · Severity: low · Ecosystem: composer — Moodle has an IDOR in badges allows disabling of arbitrary badges

OS Trackers for CVE-2025-26531

vendor priority summary link
ubuntu medium CVE-2025-26531 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-26531

Affected software / configurations for CVE-2025-26531

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-26531

cvelogic Threat Intelligence