CVE-2022-37191
Published: 13 September 2022
Summary
CVE-2022-37191 is a medium-severity Inclusion of Functionality from Untrusted Control Sphere (CWE-829) vulnerability in Cuppacms Cuppacms. Its CVSS base score is 6.5 (Medium).
Operationally, ranked in the top 3.0% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
CuppaCMS version 1.0 is affected by a local file inclusion vulnerability in the cuppa/api/index.php component. The flaw permits an authenticated user to supply an LFI payload through the function parameter of a crafted POST request, resulting in disclosure of arbitrary system files. The issue carries a CVSS 3.1 base score of 6.5 with network attack vector, low complexity, and low privileges required.
An authenticated attacker can exploit the vulnerability remotely to read sensitive files on the underlying system, achieving high confidentiality impact without user interaction or scope change. Public proof-of-concept material and issue reports document the attack vector in detail.
The EPSS score for this CVE rose to a peak of 0.4674 before settling at the current value of 0.3237, indicating that exploitation interest increased measurably after public disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-39843
Vulnerability details
The component "cuppa/api/index.php" of CuppaCMS v1.0 is Vulnerable to LFI. An authenticated user can read system files via crafted POST request using [function] parameter value as LFI payload.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Limiting P2P file sharing technology reduces inclusion of functionality or resources from untrusted external control spheres.
Enforcing installation policies prevents users from including functionality obtained from untrusted control spheres.
The inventory process requires identifying and recording the origin of all components, making inclusion of functionality from untrusted control spheres easier to detect during reviews.
Requiring approval and monitoring of maintenance tools prevents inclusion and execution of functionality obtained from untrusted sources.
Unowned portable devices represent untrusted control spheres; the prohibition prevents inclusion of functionality or data from such sources.
Strategy mandates assessment of third-party components and suppliers, directly reducing inclusion of functionality from untrusted control spheres.
Procedures can mandate supply-chain vetting and restrictions on functionality obtained from untrusted third-party or external control spheres.
Requires use of trusted sources and provenance tracking, tangibly limiting inclusion of functionality from untrusted control spheres.