CVE-2024-4867
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WSO2 API Manager developer portal accepts user-supplied input without enforcing expected validation constraints or proper output encoding. This deficiency allows a malicious actor to inject script content that is executed within the context of a user's browser. By leveraging this cross-site scripting vulnerability, a malicious actor can cause the browser to redirect to a malicious website, make changes to the UI of the web page, or retrieve information from the browser. However, session hijacking is not possible as all session-related sensitive cookies are protected by the httpOnly flag.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a stored cross-site scripting (XSS) vulnerability in WSO2 API Manager's developer portal where user-supplied input is accepted without proper validation constraints or output encoding. An attacker can inject malicious script content that executes within a victim's browser context, enabling UI manipulation, browser redirects, or sensitive data exfiltration. Session hijacking is mitigated by httpOnly flag protection on session cookies.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 3.2.0, < 3.2.0.408>= 3.2.1, < 3.2.1.32>= 4.0.0, < 4.0.0.293>= 4.1.0, < 4.1.0.187CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify WSO2 API Manager installation pathLocate the product installation directory. The version is typically stored in a file named 'carbon.xml' or can be retrieved by examining the product's runtime files. Common paths include /opt/wso2/am or C:\Program Files\WSO2\API Manager. Check for a 'repository' folder containing 'components' subdirectories.Affected if The installation path cannot be located or is not a WSO2 API Manager installation.
-
Determine installed WSO2 API Manager versionLook for the version file in the product distribution. The version information is commonly found in the product's release information file or by examining the product's build configuration. Compare the discovered version number against the affected ranges: 3.2.0 through 3.2.0.407, 3.2.1 through 3.2.1.31, 4.0.0 through 4.0.0.292, and 4.1.0 through 4.1.0.186.Affected if The installed version falls within any of the affected ranges listed.
-
Verify developer portal is exposedCheck if the developer portal component is accessible. The developer portal is typically accessed via the /devportal or /apistore endpoint. Confirm the portal is network-accessible by verifying the web application is running and responding to requests.Affected if The developer portal is enabled and accessible over the network.
-
Check for recent security patchesReview the product's patch history or changelog if available. Determine if any security updates addressing this specific CVE have been applied. This may be visible in patch notes, update logs, or the product's internal version tracking.Affected if No security patches for CVE-2024-4867 have been applied to the installation.
The environment is affected if WSO2 API Manager is installed with the developer portal accessible and the installed version falls within any of the vulnerable version ranges (3.2.0-3.2.0.407, 3.2.1-3.2.1.31, 4.0.0-4.0.0.292, or 4.1.0-4.1.0.186) without the corresponding security patch applied.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.2.0.4083.2.1.324.0.0.293
Implement strict input validation for all user-supplied data in the developer portal combined with proper output encoding (context-aware escaping) before rendering any user-controlled content in HTML/JavaScript contexts.
Upgrade to 3.2.0.408 (for 3.2.0.x), 3.2.1.32 (for 3.2.1.x), 4.0.0.293 (for 4.0.0.x), or 4.1.0.187 (for 4.1.0.x)
- 1. Back up your current WSO2 API Manager installation, database, and configuration files
- 2. Identify your current version from the affected version ranges (3.2.0.x, 3.2.1.x, 4.0.0.x, or 4.1.0.x)
- 3. Download the corresponding fixed release: 3.2.0.408, 3.2.1.32, 4.0.0.293, or 4.1.0.187
- 4. Stop the running WSO2 API Manager instance
- 5. Restore configurations from backup to the new installation if using a fresh install, or use the migration client if upgrading across major versions
- 6. Start the WSO2 API Manager and verify all services are running
- 7. Test the developer portal to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4867 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-4867 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data