CVE-2022-36699

HIGHNVD 8.88.8—

8.8

Ingredients Stock Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /categories/manage_category.php.

CVSS v3: 8.8
EG Score: 8.8(medium)
EPSS: 55.8%
KEV: Not listed

Published

August 25, 2022

Last Modified

November 21, 2024

References (2)

cve@mitrehttps://github.com/k0xx11/vul-wiki/blob/master/vendors/oretnom23/ingredients-stock-management-system/SQLi-11.md
af854a3a-2127-422b-91ae-364da2661108https://github.com/k0xx11/vul-wiki/blob/master/vendors/oretnom23/ingredients-stock-management-system/SQLi-11.md

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-89SQL Injection

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

2026-06-08 14:15 UTCEPSS rescore
2026-06-08 14:15 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-07 15:23 UTCEPSS rescore
2026-06-06 13:46 UTCEPSS rescore
2026-06-06 13:46 UTCEPSS rescore
2026-06-06 13:46 UTCEPSS rescore
2026-06-05 22:46 UTCEPSS rescore
2026-06-05 22:45 UTCEPSS rescore
2026-06-05 06:09 UTCEPSS rescore
2026-06-05 06:09 UTCEPSS rescore
2026-06-04 13:11 UTCEPSS rescore
2026-06-04 13:11 UTCEPSS rescore
2026-06-02 20:11 UTCEPSS rescore
2026-06-02 20:11 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-06-01 13:50 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore
2026-05-31 22:29 UTCEPSS rescore

Frequently asked(5)

What is CVE-2022-36699?

CVE-2022-36699 is a high vulnerability published on August 25, 2022. Ingredients Stock Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /categories/manage_category.php.

When was CVE-2022-36699 disclosed?

CVE-2022-36699 was first published in the National Vulnerability Database on August 25, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-36699 actively exploited?

CVE-2022-36699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 55.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-36699?

CVE-2022-36699 has a CVSS v3 base score of 8.8 (NVD).

How do I remediate CVE-2022-36699?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-36699, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-36699

Explore →

Is Your Infrastructure Affected by CVE-2022-36699?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2022-36699

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-36699?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same CWE)