Security readout for executives and security teams
Plain-English summary
CVE-2024-50808 is a high-severity code injection issue reported in SeaCms 13.1. A low-privileged authenticated user may be able to cause unauthorized code execution through unsafe handling of a notification parameter in the backend. That creates serious confidentiality, integrity, and availability risk where SeaCms administrative functionality is reachable.
Executive priority
Treat this as a high-priority application risk if SeaCms 13.1 is in use. The issue can impact full system confidentiality, integrity, and availability, but the current evidence does not support an active-exploitation claim.
Technical view
The CVE describes CWE-94 code injection in SeaCms 13.1, specifically unsafe handling of the "notify" variable in admin_notify.php within the backend member message notification module. CVSS 3.1 is 8.8 with network attack vector, low attack complexity, low privileges required, no user interaction, and high CIA impact.
Likely exposure
Exposure is most likely in environments running SeaCms 13.1 where the backend notification/admin area is reachable by authenticated low-privileged users. The CVE metadata has incomplete affected-product fields, so asset validation is important.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. A public GitHub reference is listed, but the provided evidence is insufficient to claim exploitation in the wild.
Researcher notes
Key gaps are incomplete CPE/vendor metadata and no named patch in the provided sources. Scope conclusions should be limited to SeaCms 13.1 as described in the CVE text and the referenced GitHub disclosure.
Mitigation direction
- Identify any SeaCms 13.1 deployments and prioritize them for review.
- Check SeaCms or maintainer guidance for a fixed release or official workaround.
- Restrict backend/admin access to trusted users and networks.
- Review admin_notify.php handling of the notify variable if maintaining local code.
- Monitor backend notification activity for unusual or unauthorized changes.
Validation and detection
- Confirm whether SeaCms 13.1 is present in production or internet-adjacent systems.
- Verify whether admin_notify.php and the notification module are deployed.
- Review role access to backend member message notification functions.
- Check logs for suspicious backend notification requests or unexpected code changes.
- Track the CVE record and GitHub reference for remediation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2024-50808 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/v9d0g/CVEs/blob/main/CVE-2024-50808.mdCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.