PNG to JPG <= 5.8 - Cross-Site Request Forgery leading to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 4.1
- Affected Plugin
- PNG to JPG
- Affected Version
<= 4.0- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-29430
At a glance
CVE-2022-29430 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the PNG to JPG WordPress plugin, affecting versions <= 4.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.1; sites on affected versions should update now. Disclosed May 2022, reported by R3N0.
Vulnerability Overview
Cross-Site Scripting (XSS) vulnerability in KubiQ's PNG to JPG plugin <= 4.0 at WordPress via Cross-Site Request Forgery (CSRF). Vulnerable parameter &jpg_quality.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in PNG to JPG <= 4.0 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For PNG to JPG the fix is 4.1: builds <= 4.0 are affected, anything from 4.1 onward is not.
Remediation
Update to version 4.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to PNG to JPG: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: PNG to JPG 4.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C