CVE-2022-29464: Certain WSO2 products allow unrestricted file upload with resultant remote code execution.
Noroxi assessment
Priority: Now (action score 99/100)
- CISA has confirmed exploitation in the wild (Apr 25, 2022); it is known to be used in ransomware campaigns. Remediation deadline for US federal agencies: May 16, 2022.
- A ready-made attack module is public (Metasploit, Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 99.9% (FIRST EPSS); higher than 99.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Patch today or shut off access. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
Certain WSO2 products allow unrestricted file upload with resultant remote code execution. The attacker must use a /fileupload endpoint with a Content-Disposition directory traversal sequence to reach a directory under the web root, such as a ../../../../repository/deployment/server/webapps directory. This affects WSO2 API Manager 2.2.0 up to 4.0.0, WSO2 Identity Server 5.2.0 up to 5.11.0, WSO2 Identity Server Analytics 5.4.0, 5.4.1, 5.5.0 and 5.6.0, WSO2 Identity Server as Key Manager 5.3.0 up to 5.11.0, WSO2 Enterprise Integrator 6.2.0 up to 6.6.0, WSO2 Open Banking AM 1.4.0 up to 2.0.0 and WSO2 Open Banking KM 1.4.0, up to 2.0.0.
- Published
- Apr 18, 2022
- Updated
- Jun 17, 2026
- EPSS
- 99.9% · 99th percentile
- CWE
- CWE-22
Report tools
Action score
99
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 30 / 30 · 99.9%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · mitre
- 9.8
- agree
CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Apr 25, 2022. That signals real attacks, not theory.
Remediation deadline for US federal agencies: May 16, 2022.
Known to be used in ransomware campaigns.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| wso2 | api manager | cpe:2.3:a:wso2:api_manager |
| wso2 | enterprise integrator | cpe:2.3:a:wso2:enterprise_integrator |
| wso2 | identity server | cpe:2.3:a:wso2:identity_server |
| wso2 | identity server analytics | cpe:2.3:a:wso2:identity_server_analytics |
| wso2 | identity server as key manager | cpe:2.3:a:wso2:identity_server_as_key_manager |
| wso2 | open banking am | cpe:2.3:a:wso2:open_banking_am |
| wso2 | open banking iam | cpe:2.3:a:wso2:open_banking_iam |
| wso2 | open banking km | cpe:2.3:a:wso2:open_banking_km |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- wso2 api manager2.2.0 and later · up to 4.0.0 inclusive
- wso2 enterprise integrator6.2.0 and later · up to 6.6.0 inclusive
- wso2 identity server5.2.0 and later · up to 5.11.0 inclusive
- wso2 identity server analytics5.4.0
- wso2 identity server analytics5.4.1
- wso2 identity server analytics5.5.0
- wso2 identity server analytics5.6.0
- wso2 identity server as key manager5.3.0 and later · up to 5.10.0 inclusive
+3 more rows
- wso2 open banking am1.3.0 and later · up to 2.0.0 inclusive
- wso2 open banking iam2.0.0
- wso2 open banking km1.3.0 and later · up to 1.5.0 inclusive
Same product
wso2: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-24589The Management Console in WSO2 API Manager through 3.1.0 and API Microgateway 2.2.0 allows XML External Entity injection (XXE) attacks.44Plan
- CVE-2026-2053Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager40Plan
- CVE-2020-13226WSO2 API Manager 3.0.0 does not properly restrict outbound network access from a Publisher node, opening up the possibility of SSRF to this…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-17453Apr 5, 2021 · WSO2 Management Console through 5.10 allows XSS via the carbon/admin/login.jsp msgId parameter.32Monitor
- ← EarlierCVE-2021-36760Dec 7, 2021 · In accountrecoveryendpoint/recoverpassword.do in WSO2 Identity Server 5.7.0, it is possible to perform a DOM-Based XSS attack affecting the…24Monitor
- Later →CVE-2022-29548Apr 20, 2022 · A reflected XSS issue exists in the Management Console of several WSO2 products.36Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Metasploit module ×1
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×29
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | 29 repositories | 2022-04-20 → 2025-01-17 |
| Metasploit module | exploit/multi/http/wso2_file_upload_rceWSO2 Arbitrary File Upload to RCEexploit | 2022-04-01 |
| Nuclei detection template | Nuclei template CVE-2022-29464 | — |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Metasploit-18 d
- Published
- First PoC+1 d
- CISA KEV+6 d
- TodayNov 13, 2026+1670 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.