How severe is CVE-2022-0596?

CVE-2022-0596 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-0596?

CVE-2022-0596 affects the following packages: microweber/microweber (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2022-0596?

Update microweber/microweber to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0596 is resolved across your whole dependency graph.

How do I detect CVE-2022-0596 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microweber/microweber, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-0596 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2022-0596 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-0596, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-0596?

CVE-2022-0596 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-0596?

CVE-2022-0596 is classified as CWE-1284 (CWE-1284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-0596 published, and has it been updated?

CVE-2022-0596 was published on February 15, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2022-0596 — microweber

MEDIUMFix: microweber/microweber@91a9d89

CVE-2022-0596 is a medium-severity (CVSS 5.4) CWE-1284 vulnerability in microweber/microweber. 1 public exploit reference exists, so weaponization risk is real. A fix is available for microweber/microweber — see the affected versions and patch details below.

Improper Validation of Specified Quantity in Input in microweber/microweber

Also known asGHSA-vpq7-m4qm-p2gp

Published

Feb 15, 2022

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Oct 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-0596 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘microweber/microweber

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Microweber prior to version 1.2.11 can have a negative product amount. This could allow an attacker to manipulate the total value and get products for free.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`microweber/microweber`	all versions	1.2.11`composer require microweber/microweber:^1.2.11`

Affected Products

1 product · 1 configurations

Application

microwebermicroweber

< 1.2.11

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Improper Validation of Specified Quantity in Input in Packagist microweb…

huntr.devNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for microweber/microweber, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update microweber/microweber to 1.2.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-0596 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Microweber prior to version 1.2.11 can have a negative product amount. This could allow an attacker to manipulate the total value and get products for free.

O3 Security · Impact-Aware SCA

Is CVE-2022-0596 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

CWE Classification

CWE-1284CWE-1284

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Feb 15, 2022

First exploit

Feb 23, 2022

Last updated

Aug 12, 2026

Identifiers

CVE-2022-0596

GHSA-vpq7-m4qm-p2gp

References

Advisorygithub.com Advisorynvd.nist.gov Fixgithub.com Webhuntr.dev Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 5 of 8 other CVEs affecting microweber/microweber are rated as high or higher (top: moderate).

CVE-2026-12198CVE-2025-70791CVE-2025-70792CVE-2025-51504CVE-2025-51501CVE-2025-51502CVE-2025-51503CVE-2025-34076

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 12, 2026