Cyber Resilience

CVE-2022-4050

CriticalPublic PoC

Published: 19 December 2022

Published
19 December 2022
Modified
17 April 2025
KEV Added
Patch
CVSS Score v3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.7725 99.0th percentile
Risk Priority 66 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2022-4050 is a critical-severity an unspecified weakness vulnerability in Beardev Joomsport. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 1.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

The JoomSport WordPress plugin before version 5.2.8 contains a SQL injection vulnerability stemming from inadequate sanitization and escaping of a parameter incorporated into a SQL statement. The affected component is this plugin running on WordPress sites, with the issue assigned a CVSS 3.1 score of 9.8 reflecting network-exploitable impact on confidentiality, integrity, and availability.

Unauthenticated attackers can exploit the flaw remotely without user interaction or credentials, enabling them to manipulate database queries and potentially extract, modify, or delete data or escalate to broader system compromise.

References from WPScan document the vulnerability in detail and indicate that updating the JoomSport plugin to version 5.2.8 or later addresses the injection risk by correcting the parameter handling. The EPSS score reached a peak of 0.8445 with a current value of 0.7725, indicating sustained exploitation interest following disclosure.

EU & UK References

Vulnerability details

The JoomSport WordPress plugin before 5.2.8 does not properly sanitise and escape a parameter before using it in a SQL statement, leading to a SQL injection exploitable by unauthenticated users

CWE(s)
None listed

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

beardev
joomsport
≤ 5.2.8

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References