LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40925: Zoo Management System v1.0 has an arbitrary file upload vulnerability in the picture upload point of the "s...

Zoo Management System v1.0 has an arbitrary file upload vulnerability in the picture upload point of the "save_event" file of the "Events" module in the background management system.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-40925 is a high-severity file upload flaw in Zoo Management System v1.0. An attacker with high-level admin access could abuse the Events module picture upload path to upload unsafe files, potentially compromising confidentiality, integrity, and availability.

Executive priority

Treat as important where the application is internet-accessible or admins are shared, outsourced, or weakly controlled. The high privilege requirement lowers likelihood, but successful abuse could lead to full system compromise.

Technical view

The CVE describes CWE-434 unrestricted upload of dangerous file types in the background management system’s Events module, specifically the save_event picture upload point. CVSS 3.1 is 7.2 with network attack vector, low complexity, high privileges required, no user interaction, and high CIA impact.

Likely exposure

Exposure appears limited to deployments of Zoo Management System v1.0 with the background management interface reachable by users who can access the Events administration functions. The CVE affected-product metadata is incomplete, so asset owners must verify product lineage manually.

Exploitation context

The source bundle does not cite CISA KEV listing or active exploitation. A public GitHub vulnerability report is referenced, but the available CVE data only supports saying the issue is publicly disclosed, not exploited in the wild.

Researcher notes

Evidence is narrow: CVE description, CVSS, CWE-434 classification, and one public GitHub report. Product/vendor fields are listed as n/a in the supplied data, so validate the exact application source before broad prioritization.

Mitigation direction

  • Check project or vendor channels for patched releases or official guidance.
  • Restrict background management access to trusted administrators and networks.
  • Disable or limit Events picture uploads if operationally acceptable.
  • Review upload handling for server-side file type and execution controls.
  • Monitor uploaded files and web directories for unexpected executable content.

Validation and detection

  • Confirm whether Zoo Management System v1.0 is deployed anywhere.
  • Identify who can access the background Events management module.
  • Review the save_event picture upload handling and storage location.
  • Check web server configuration for executable uploads in media directories.
  • Look for unexpected files uploaded through Events administration paths.
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-2022-40925 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
High
CVSS
7.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
0Timeline events
0ADP providers
2Source links

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
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2022-40925Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/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
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.