# CVE-2025-12317: Improper Token Revocation via SOAP Services in Multiple WSO2 Products Allows Retained Access Privileges

> Attackers retain access privileges after role revocation due to improper token invalidation in WSO2 products, allowing unauthorized actions until token expiration.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-257q-prhp-qgwp

## What is CVE-2025-12317?

CVE-2025-12317 is a medium-severity authentication bypass vulnerability in WSO2 Enterprise Integrator, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

When internal roles are removed from a user within the WSO2 product, the system fails to invalidate any previously issued authentication tokens associated with that user.

This vulnerability could allow users to retain their previous access privileges even after their roles have been revoked. As a result, a user can continue to perform unauthorized actions or access restricted resources until the expired tokens naturally expire.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2025-12317?


## How do I fix CVE-2025-12317?

No fix has been published for CVE-2025-12317 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12317 being exploited?

There is no known exploitation of CVE-2025-12317 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12317 and fix it if it is affected.

What it is: CVE-2025-12317 is a medium-severity authentication bypass vulnerability in WSO2 Enterprise Integrator, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12317 in the wild and no public exploit code.

Affected product: WSO2 Enterprise Integrator. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12317/ (Markdown: https://insights.sbomify.com/CVE-2025-12317/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12317
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12317
- OSV: https://osv.dev/vulnerability/CVE-2025-12317

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12317/
Summaries are generated and may contain mistakes; the official description above is the record.