CVE-2024-50808: SeaCms 13.1 is vulnerable to code injection in the notification module of the member message notification modu

This month

HIGH 8.8DOWNGRADE

CVE-2024-50808 is a high-severity flaw (CVSS 8.8) affecting seacms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

SeaCms 13.1 is vulnerable to code injection in the notification module of the member message notification module in the backend user module, due to unsafe handling of the "notify" variable in admin_notify.php.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 51%)
CISA exploited list	No
Weakness	CWE-94
Published	2024-11-08
Last modified	2026-07-05

Publisher (CNA): MITRE · Vendor: seacms

Last updated 2026-07-05 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-11-08 21:15 UTCPublished CVE record published
2026-07-05 01:20 UTCUpdated Record last modified

seacms seacms DOWNGRADE

Affected: 13.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 13.1

1. Check installed version

apt-cache policy seacms || rpm -q seacms || seacms --version

2. No fixed release: DOWNGRADE to a release before 13.1 (Debian / Ubuntu)

apt-cache madison seacms sudo apt install seacms=<VERSION_BEFORE_13.1> sudo apt-mark hold seacms

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list seacms sudo dnf downgrade seacms-<VERSION_BEFORE_13.1> sudo dnf versionlock add seacms

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-50808?

seacms: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-50808 being exploited?

CVE-2024-50808 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-50808 affect?

CVE-2024-50808 affects seacms. Severity is high (CVSS 8.8). SeaCms 13.1 is vulnerable to code injection in the notification module of the member message notification module in the backend user module, due to unsafe handling of the "notify" variable in admin_notify.php.

How urgent is CVE-2024-50808?

Priority 48/100. High severity; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2025-15003 MEDIUM 4.7 UPGRADE A vulnerability was found in SeaCMS up to 13.3
CVE-2025-10662 MEDIUM 4.7 UPGRADE A vulnerability has been found in SeaCMS up to 13.3
CVE-2025-11071 MEDIUM 4.7 DOWNGRADE A security vulnerability has been detected in SeaCMS 13.3.20250820
CVE-2025-50592 MEDIUM 5.4 UPGRADE Cross site scripting vulnerability in seacms before 13.2 via the vid parameter to Upload/js/player/dmplayer/pl
CVE-2025-25813 MEDIUM 5.1 DOWNGRADE SeaCMS v13.3 was discovered to contain a remote code execution (RCE) vulnerability via the component admin_fil

References

← Back to latest CVEs