LiveActive security incident?Get immediate response
CVE Record

CVE-2022-38877: Garage Management System v1.0 is vulnerable to Arbitrary code execution via ip/garage/php_action/editProduc...

Garage Management System v1.0 is vulnerable to Arbitrary code execution via ip/garage/php_action/editProductImage.php?id=1.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-38877 is a high-severity flaw in Garage Management System v1.0 that can allow arbitrary code execution through the product image editing function. The available record indicates an attacker needs high privileges, so this is most urgent where admin access is shared, weakly controlled, or exposed over the internet.

Executive priority

Treat as a high-priority internal application risk, especially if the system is internet-facing or admin accounts are broadly shared. Business urgency is lower than unauthenticated RCE, but compromise of an administrator could lead directly to server takeover.

Technical view

The CVE describes arbitrary code execution in `php_action/editProductImage.php?id=1`, categorized as CWE-434. CVSS 3.1 is 7.2 with network attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on deployed Garage Management System v1.0 instances with reachable administrative product-image functionality. The CVE metadata does not provide CPEs, vendor identifiers, hosting patterns, or package names, so inventory confirmation is required.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. A public GitHub report is referenced. The CVSS vector indicates exploitation requires high privileges but can be performed remotely without user interaction once that access exists.

Researcher notes

Evidence is sparse: the CVE identifies the vulnerable endpoint and CWE, but affected metadata is incomplete and no fix is named in the provided sources. Validate version and deployment context before asserting exposure or remediation status.

Mitigation direction

  • Inventory any Garage Management System v1.0 deployments and owners.
  • Check the project or vendor source for patch or upgrade guidance.
  • Restrict administrative access to trusted networks and named users.
  • Review upload handling for executable file acceptance and server execution paths.
  • Retire or isolate the application if no maintained fix is available.

Validation and detection

  • Confirm whether `editProductImage.php` exists in deployed instances.
  • Verify only authorized administrators can access product image editing.
  • Check web server logs for unusual product image update activity.
  • Review uploaded image directories for unexpected executable files.
  • Document findings against Garage Management System version evidence.
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

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-38877 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-38877Attack 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.