Guzzle <= 6.5.7 and 7.0-7.4.4 — Information Exposure
CVE-2022-31090Published · Updated Action summary
Affected: ≤2.2.2Update to 2.2.3 or newer
All remediation steps- Severity
- High7.7
- CVSS
- 7.7CVSS 3.1 · CNA (Wordfence)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:NWhat does this vector mean?
AV:NAttack vector- Network
AC:LAttack complexity- Low
PR:LPrivileges required- Low
UI:NUser interaction- None
S:CScope- Changed
C:HConfidentiality- High
I:NIntegrity- None
A:NAvailability- None
- Weakness
- CWE-200 Information Exposure
- Required access
- Unknown
- Exploit prediction (EPSS)
- No score
- CISA KEV
- Not listed
On this page8
Am I affected?
W3 Total Cache w3-total-cache
- Affected≤ 2.2.2
- Patched in2.2.3
Update to 2.2.3 or newer.
You are affected if you run ≤ 2.2.2. Version 2.2.3 and later are not affected by this issue.
- Check your version: in wp-admin go to Plugins → Installed Plugins and read the version under W3 Total Cache.
- No admin access? Run a passive check of your site. It reads public files only.
What to do
- Update to version 2.2.3, or a newer patched version
- Rotate administrator passwords and application secrets if the site ran a vulnerable version while publicly reachable.
- Watch W3 Total Cache to get an email when the next vulnerability is published.
Advisory
Source description from Wordfence Intelligence.
Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin (change in host, scheme or port), if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to the new request. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl. *Please note that while some WordPress plugins and themes may use this as a dependency, they may not be directly exploitable.
Exploits & references
Proof-of-concept & detection
No public proof-of-concept or detection template is known for this vulnerability.
Advisories & patches
- Advisorywordfence.com
Related CVEs
More in W3 Total Cache
All 41| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium5.4 | Unauthenticated Stored Cross-Site Scripting via Comment Content via Predictable Minify Placeholder ≤2.10.7Update to 2.11.0 | CVE-2026-120019 | |
| High7.2 | Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry ≤2.10.7Update to 2.11.0 | CVE-2026-111254 | |
| High7.2 | Unauthenticated Stored Cross-Site Scripting ≤2.10.7Update to 2.11.0 | CVE-2026-114178 | |
| Medium6.5 | Authenticated (Author+) Path Traversal ≤2.10.5Update to 2.10.6 | CVE-2026-107321 | |
| High7.2 | Unauthenticated Stored Cross-Site Scripting via Comment Content ≤2.10.6Update to 2.10.7 | CVE-2026-87920 |
- Medium5.4Unauthenticated Stored Cross-Site Scripting via Comment Content via Predictable Minify Placeholder
≤2.10.7Update to 2.11.0
- High7.2Unauthenticated Stored Cross-Site Scripting via Comment Content Cached as HTML after License Expiry
≤2.10.7Update to 2.11.0
- High7.2Unauthenticated Stored Cross-Site Scripting
≤2.10.7Update to 2.11.0
- Medium6.5Authenticated (Author+) Path Traversal
≤2.10.5Update to 2.10.6
- High7.2Unauthenticated Stored Cross-Site Scripting via Comment Content
≤2.10.6Update to 2.10.7
Same weakness (Information Exposure)
All Information Exposure| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High7.2 | Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header | CVE-2026-120688 | |
| Critical9.8 | Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission | CVE-2026-125055 | |
| Critical9.8 | Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter | CVE-2026-119077 | |
| Medium5.3 | Unauthenticated Sensitive Information Exposure in 'search' Parameter | CVE-2026-121518 |
- High7.2Unauthenticated Stored Cross-Site Scripting via Comment User-Agent Header
EZ SQL Reports Shortcode Widget and DB Backup
≤5.25.25Update to 5.26.45
- Critical9.8Unauthenticated Arbitrary File Upload via File Upload via Public Form Submission
Chatterbug Forms – Fast, Flexible WordPress Form Builder
≤1.0.2Update to 1.1
- Critical9.8Unauthenticated PHP Object Injection to Remote Code Execution via 'form' Parameter
ELEX WordPress HelpDesk & Customer Ticketing System
≤3.3.9Update to 3.4.0
- Medium5.3Unauthenticated Sensitive Information Exposure in 'search' Parameter
Customer Reviews for WooCommerce
≤5.127.0Update to 5.128.0
Timeline
CVE published
Severity high, CVSS 7.7
Record last updated
Sources & licenses
Wordfence record- Vulnerability data
- Wordfence Intelligence. Copyright 2012-2026 Defiant Inc. Licensed under the CC BY-SA 4.0.
- CVE® identifiers
- Copyright 1999-2026 The MITRE Corporation. Used under the CVE Program. CVE® is a registered trademark of The MITRE Corporation.
- CVSS / CWE
- National Vulnerability Database (NVD), shown unmodified. This product uses the NVD API but is not endorsed or certified by the NVD.
- VulnCrest content
- Summary, remediation guidance and page layout © VulnCrest. Not sourced from NVD.