LiveActive security incident?Get immediate response
CVE Record

CVE-2024-32161: jizhiCMS 2.5 suffers from a File upload vulnerability.

jizhiCMS 2.5 suffers from a File upload vulnerability.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

jizhiCMS 2.5 is reported to allow unsafe file uploads. If exposed, this can let an unauthenticated remote attacker affect confidentiality, integrity, and availability. The public bundle does not name a fixed version or vendor mitigation, so teams should verify use quickly and seek authoritative project guidance.

Executive priority

Treat as urgent for any internet-facing jizhiCMS 2.5 deployment. The rating implies full business impact is possible, but remediation depends on confirming affected assets and obtaining vendor guidance.

Technical view

CVE-2024-32161 is categorized as CWE-434, unrestricted upload of a dangerous file. The CVSS 3.1 vector is network, low complexity, no privileges, no user interaction, unchanged scope, with high C/I/A impact. The provided sources do not specify an endpoint, patch, or detailed affected CPEs.

Likely exposure

Likely exposure is organizations running jizhiCMS 2.5, especially internet-facing CMS or upload functionality. The source bundle lists affected vendor/product/version fields as n/a, so confirm exposure through asset inventory and application owner validation.

Exploitation context

The CVE has a critical CVSS score, but the source bundle does not show CISA KEV listing or cited evidence of active exploitation. A public GitHub reference exists, so defenders should assume technical details may be accessible.

Researcher notes

The provided record is thin: affected CPEs are absent and the description only states file upload vulnerability. Avoid assuming exploit mechanics, endpoints, or fixed versions without reviewing authoritative project advisories or validated test evidence.

Mitigation direction

  • Identify any jizhiCMS 2.5 deployments and owners.
  • Check official project or vendor guidance for a fixed release.
  • Restrict public access to upload-capable CMS surfaces.
  • Disable nonessential upload features until guidance is confirmed.
  • Monitor web and file-write activity around CMS upload paths.

Validation and detection

  • Confirm application name and version from inventory or owner records.
  • Review exposure of CMS admin and upload endpoints.
  • Check whether uploaded files can execute server-side code.
  • Look for unexpected files created through CMS upload workflows.
  • Verify logs for unauthenticated upload attempts or anomalies.
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 · medium confidence lookup

CWE-434: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection 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 lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-32161 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.8 (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:H

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
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical 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.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-32161Attack 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:H

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
CVECVE Program Container
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-434 · source CWE mapping

Unrestricted Upload of File with Dangerous Type

Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.