LiveActive security incident?Get immediate response
CVE Record

CVE-2024-54879: SeaCMS V13.1 is vulnerable to Incorrect Access Control.

SeaCMS V13.1 is vulnerable to Incorrect Access Control. A logic flaw can be exploited by an attacker to allow any user to recharge members indefinitely.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

SeaCMS V13.1 has an access-control flaw that can let users repeatedly recharge member accounts. For an exposed deployment, this could directly affect account balances, revenue controls, and trust in transaction records. The provided sources do not name a vendor patch or fixed version.

Executive priority

Treat this as urgent for any SeaCMS V13.1 system handling payments, balances, or member credits. Prioritize confirmation, containment, and vendor remediation tracking because the described impact affects financial integrity.

Technical view

The CVE describes CWE-281 Incorrect Access Control in SeaCMS V13.1. The stated logic flaw allows indefinite member recharge by any user. CVSS 3.1 is 9.1, network exploitable, low complexity, no privileges, no user interaction, with high confidentiality and integrity impact and no availability impact.

Likely exposure

Exposure is most likely where SeaCMS V13.1 is deployed and member recharge functionality is reachable. The CVE record lists affected vendor, product, CPE, and versions as n/a, so asset matching may require manual confirmation.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. A public blog reference exists, but the provided evidence is insufficient to claim exploitation in the wild.

Researcher notes

Evidence is thin: the CVE description, CVSS vector, CWE, and one public reference are available, but affected-product metadata is incomplete. Do not assume broader SeaCMS versions are affected without vendor or code evidence.

Mitigation direction

  • Check SeaCMS vendor guidance for an advisory, patch, or fixed release.
  • Restrict access to member recharge functions until remediation is confirmed.
  • Review recharge and balance records for suspicious repeated activity.
  • Add compensating access controls around affected workflows where feasible.
  • Monitor public CVE and vendor sources for updated affected-version details.

Validation and detection

  • Identify all SeaCMS deployments and confirm whether version 13.1 is present.
  • Verify whether member recharge workflows enforce intended authorization rules.
  • Review logs for repeated recharge attempts or unusual balance changes.
  • Check whether current builds include a vendor-confirmed fix.
  • Document uncertainty where CPE or affected-version metadata is missing.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-281: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookup
cve · low confidence lookup

CVE-2024-54879 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2024-54879Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-281 · source CWE mapping

Improper Preservation of Permissions

Improper Preservation of Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.