CVE-2022-36667: Garage Management System 1.0 is vulnerable to the Remote Code Execution (RCE) due to the lack of filtering fro

This week

HIGH 8.8DOWNGRADE

CVE-2022-36667 is a high-severity flaw (CVSS 8.8) affecting garage management system. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Garage Management System 1.0 is vulnerable to the Remote Code Execution (RCE) due to the lack of filtering from the file upload function. The vulnerability exist during adding parts and from the upload function, the attacker can upload PHP Reverse Shell straight away to gain RCE.

Why this priority

High severity
EPSS top 2%: very likely to be exploited
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	24.9% (top 2%)
CISA exploited list	No
Weakness	CWE-434
Published	2022-09-14
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: garage management system project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-09-14 11:15 UTCPublished CVE record published
2026-06-17 04:53 UTCUpdated Record last modified

garage management system project garage management system DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy garage-management-system || rpm -q garage-management-system || garage-management-system --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison garage-management-system sudo apt install garage-management-system=<VERSION_BEFORE_1.0> sudo apt-mark hold garage-management-system

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list garage-management-system sudo dnf downgrade garage-management-system-<VERSION_BEFORE_1.0> sudo dnf versionlock add garage-management-system

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-36667?

garage management system: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-36667 being exploited?

CVE-2022-36667 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-36667 affect?

CVE-2022-36667 affects garage management system. Severity is high (CVSS 8.8). Garage Management System 1.0 is vulnerable to the Remote Code Execution (RCE) due to the lack of filtering from the file upload function. The vulnerability exist during adding parts and from the upload function, the attacker can upload PHP

How urgent is CVE-2022-36667?

Priority 60/100. High severity; EPSS top 2%: very likely to be exploited; Public exploit reference

Software pages

PHP vulnerabilities

Related CVEs

CVE-2022-44279 MEDIUM 6.1 DOWNGRADE Garage Management System v1.0 is vulnerable to Cross Site Scripting (XSS) via /garage/php_action/createBrand.p
CVE-2022-41358 MEDIUM 5.4 DOWNGRADE A stored cross-site scripting (XSS) vulnerability in Garage Management System v1.0 allows attackers to execute
CVE-2022-38877 HIGH 7.2 DOWNGRADE Garage Management System v1.0 is vulnerable to Arbitrary code execution via ip/garage/php_action/editProductIm
CVE-2022-38610 HIGH 7.2 DOWNGRADE Garage Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at
CVE-2022-38606 HIGH 7.2 DOWNGRADE Garage Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at

References

← Back to latest CVEs