Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2025-13590 critical CVSS 9.1

Unrestricted File Upload in org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 (CVE-2025-13590)

Summary

vulnerability in org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 (CVE-2025-13590). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `9.32.167` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2025-13590** has been found in org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1. Successful exploitation can lead to full system takeover. CVSS score: 9.1/10. What to do: upgrade org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 to **9.32.167** or later. If unsure, ask your IT team or search "org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 CVE-2025-13590" on the vendor's site.
CVE-2025-13590 (org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1) — CWE-434 / CVSS v3 9.1 Attack vector: remote (network-reachable) / no user interaction Patched: `9.32.167` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-434) exists in org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1.
📍 Affected scope
org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 — .
🔥 Severity
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **9.32.167**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1 to 9.32.167

    ステージング環境で 9.32.167 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.wso2.carbon.apimgt:org.wso2.carbon.apimgt.rest.api.admin.v1
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.32.167"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →