guzzlehttp/psr7 <= 1.84 and 2.0.0-2.1.0 - Improper Input Validation
Strategic Overview
- Status
- Patched in 1.0.5
- Affected Plugin
- Insert Special Characters
- Affected Version
<= 1.0.4- CVSS
- 7.5High
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE-2022-24775
At a glance
CVE-2022-24775 is a high-severity Improper Input Validation vulnerability in the Insert Special Characters WordPress plugin, affecting versions <= 1.0.4. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.0.5; sites on affected versions should update now. Disclosed July 2022.
Vulnerability Overview
guzzlehttp/psr7 is a PSR-7 HTTP message library. Versions prior to 1.8.4 and 2.1.1 are vulnerable to improper header parsing. An attacker could sneak in a new line character and pass untrusted values. The issue is patched in 1.8.4 and 2.1.1. There are currently no known workarounds. Some WordPress plugins and themes use this dependency though that doesn’t necessarily mean the plugin itself is vulnerable to exploitation.
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, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-20: Improper Input Validation
Reaching this weakness in Insert Special Characters <= 1.0.4 takes a caller who can reach the endpoint. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.
The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For Insert Special Characters the fix is 1.0.5: builds <= 1.0.4 are affected, anything from 1.0.5 onward is not.
Remediation
Update to version 1.0.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Insert Special Characters: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Insert Special Characters 1.0.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Insert Special Characters
- 9.8CVE-2022-25912: simple-git < 3.15.0 Remote Code Execution
CVE-2022-25912 - 9.8Minimist <= 1.2.5 Prototype Pollution
- 7.8CVE-2021-43138: async <= 2.6.3 and 3-3.2.2 - Prototype Pollution
CVE-2021-43138 - 7.5CVE-2021-43307: semver-regex and 4.0.0-4.0.3 - Regular Expression DoS
CVE-2021-43307 - 7.5ansi-regex <3.0.1 >=4.0.0 <4.1.1 >=5.0.0 <5.0.1 >=6.0.0 <6.0.1
- 5.4CVE-2022-37601: loader-utils (JS package) < 2.0.3 Prototype Pollution
CVE-2022-37601 - 3.7CVE-2022-37599: loader-utils (JS package) Regular Expression DoS
CVE-2022-37599 - 3.7CVE-2022-37603: loader-utils (JS package) Regular Expression DoS
CVE-2022-37603
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C