SeaCMS V13.1 is vulnerable to Incorrect Access Control.

published 2025-01-06 last yr. modified 2026-06-17 4mo ago also EUVD-2024-52688

cvss: 9.1; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits: 0; none known

SeaCMS V13.1 is vulnerable to Incorrect Access Control. A logic flaw can be exploited by an attacker to allow any user to register accounts in bulk.

Is CVE-2024-54880 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: last yr. (2025-01-07)

Exploit prediction

0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

blog.csdn.net https://blog.csdn.net/weixin_46686336/article/details/144797063 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CISA ADP	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Classification

Weakness

CWE-281 Improper Preservation of Permissions

References

blog.csdn.net /weixin_46686336/article/details/144797063
exploit, third-party-advisory
seacms.net /
product

Sources

CVE List CVE-2024-54880
NVD CVE-2024-54880

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.