GHSA-6qjp-wm6g-m32r
MEDIUMWSO2 incorrect authorization vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.wso2.am:am-parent☕org.wso2.am:am-parent☕org.wso2.am:am-parent☕org.wso2.is:identity-server-parent☕org.wso2.is:identity-server-parent☕org.wso2.is:identity-server-parentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An incorrect authorization vulnerability exists in multiple WSO2 products, allowing protected APIs to be accessed directly using a refresh token instead of the expected access token. Due to improper authorization checks and token mapping, session cookies are not required for API access, potentially enabling unauthorized operations.
Exploitation requires an attacker to obtain a valid refresh token of an admin user. Since refresh tokens generally have a longer expiration time, this could lead to prolonged unauthorized access to API resources, impacting data confidentiality and integrity.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.wso2.am:am-parent | ≥ 4.2.0-beta | No fix |
| ☕Maven | org.wso2.am:am-parent | ≥ 4.1.0-alpha | No fix |
| ☕Maven | org.wso2.am:am-parent | ≥ 4.0.0-beta | No fix |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 6.1.0-beta | No fix |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 6.0.0-alpha3 | No fix |
| ☕Maven | org.wso2.is:identity-server-parent | ≥ 5.11.0-alpha | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.am:am-parent. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Remediation status
No patched version of org.wso2.am:am-parent has shipped for GHSA-6qjp-wm6g-m32r yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6qjp-wm6g-m32r is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-6qjp-wm6g-m32r. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6qjp-wm6g-m32r in your dependencies?
O3 detects GHSA-6qjp-wm6g-m32r across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.