Skip to content
Noroxi
NVD / CVE Program· CNA WSO2

CVE-2025-9312: Improper Certificate-Based Authentication Enforcement in Multiple WSO2 Products

Noroxi assessment

Priority: Monitor (action score 39/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
  • 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.

Low priority for now. Update when a fix is released; 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 · FIRST EPSS

A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default configurations, the affected components may permit unauthenticated requests even when mTLS is enabled. This condition occurs when relying on the default mTLS settings for System REST APIs or when the mTLS authenticator is enabled for SOAP services, causing these interfaces to accept requests without enforcing additional authentication. Successful exploitation allows a malicious actor with network access to the affected endpoints to gain administrative privileges and perform unauthorized operations. The vulnerability is exploitable only when the impacted mTLS flows are enabled and accessible in a given deployment. Other certificate-based authentication mechanisms such as Mutual TLS OAuth client authentication and X.509 login flows are not affected, and APIs served through the API Gateway of WSO2 API Manager remain unaffected.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded
Published
Nov 18, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 16th percentile

Report tools

JSON

Action score

39

Monitor

Low priority for now.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · WSO2
9.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-9312

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
wso2api control plane
wso2api manager
wso2identity server
wso2identity server as key manager
wso2open banking am
wso2open banking iam
wso2open banking km
wso2traffic manager
wso2universal gateway

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • wso2 api control plane4.5.0
  • wso2 api manager2.2.0
  • wso2 api manager2.5.0
  • wso2 api manager2.6.0
  • wso2 api manager3.0.0
  • wso2 api manager3.1.0
  • wso2 api manager3.2.0
  • wso2 api manager3.2.1
  • wso2 api manager4.0.0
  • wso2 api manager4.1.0
  • wso2 api manager4.2.0
  • wso2 api manager4.3.0
  • wso2 api manager4.4.0
  • wso2 api manager4.5.0
  • wso2 identity server5.10.0
  • wso2 identity server5.11.0
  • wso2 identity server5.2.0
  • wso2 identity server5.3.0
  • wso2 identity server5.4.0
  • wso2 identity server5.4.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (WSO2). Independent of NVD's CPE analysis and usually ahead of it.

  • WSO2 org.wso2.carbon.identity.auth.service

    • 1.1.1 and later · before 1.1.1.2affected
    • 1.1.16 and later · before 1.1.16.3affected
    • 1.1.18 and later · before 1.1.18.4affected
    • 1.1.20 and later · before 1.1.20.5affected
    • 1.1.26 and later · before 1.1.26.7affected
    • 1.3.6 and later · before 1.3.6.8affected
    • 1.4.0 and later · before 1.4.0.18affected
    • 1.4.25 and later · before 1.4.25.24affected
    • 1.4.52 and later · before 1.4.52.4affected
    • 1.6.1 and later · before 1.6.1.11affected
  • WSO2 WSO2 API Control Plane

    • 4.5.0 and later · before 4.5.0.22affected
  • WSO2 WSO2 API Manager

    • before 2.2.0unknown
    • 2.2.0 and later · before 2.2.0.58affected
    • 2.5.0 and later · before 2.5.0.84affected
    • 2.6.0 and later · before 2.6.0.145affected
    • 3.0.0 and later · before 3.0.0.175affected
    • 3.1.0 and later · before 3.1.0.339affected
    • 3.2.0 and later · before 3.2.0.439affected
    • 3.2.1 and later · before 3.2.1.59affected
    • 4.0.0 and later · before 4.0.0.359affected
    • 4.1.0 and later · before 4.1.0.222affected
  • WSO2 WSO2 Identity Server

    • before 5.2.0unknown
    • 5.2.0 and later · before 5.2.0.33affected
    • 5.3.0 and later · before 5.3.0.34affected
    • 5.4.0 and later · before 5.4.0.33affected
    • 5.4.1 and later · before 5.4.1.37affected
    • 5.5.0 and later · before 5.5.0.51affected
    • 5.6.0 and later · before 5.6.0.59affected
    • 5.7.0 and later · before 5.7.0.125affected
    • 5.8.0 and later · before 5.8.0.109affected
    • 5.9.0 and later · before 5.9.0.168affected
  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.3.0unknown
    • 5.3.0 and later · before 5.3.0.39affected
    • 5.5.0 and later · before 5.5.0.52affected
    • 5.6.0 and later · before 5.6.0.74affected
    • 5.7.0 and later · before 5.7.0.124affected
    • 5.9.0 and later · before 5.9.0.175affected
    • 5.10.0 and later · before 5.10.0.358affected
  • WSO2 WSO2 Open Banking AM

    • before 1.4.0unknown
    • 1.4.0 and later · before 1.4.0.138affected
    • 1.5.0 and later · before 1.5.0.139affected
    • 2.0.0 and later · before 2.0.0.388affected
  • WSO2 WSO2 Open Banking IAM

    • 2.0.0 and later · before 2.0.0.408affected
  • WSO2 WSO2 Open Banking KM

    • before 1.4.0unknown
    • 1.4.0 and later · before 1.4.0.132affected
    • 1.5.0 and later · before 1.5.0.122affected
  • WSO2 WSO2 Traffic Manager

    • 4.5.0 and later · before 4.5.0.20affected
  • WSO2 WSO2 Universal Gateway

    • 4.5.0 and later · before 4.5.0.20affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-5430Authentication Bypass via JWT Algorithm Mismatch in Multiple WSO2 Products Allows Account TakeoverKEV
    77This week
  • CVE-2026-1728Privilege Escalation via System REST APIs in Multiple WSO2 Products Permits Admin Account Takeover
    39Monitor
  • CVE-2025-9152Improper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-5770Nov 5, 2025 · Reflected Cross-Site Scripting (XSS) in Authentication Endpoints of Multiple WSO2 Products
    24Monitor
  • ← EarlierCVE-2025-6670Nov 18, 2025 · Cross-Site Request Forgery (CSRF) in Multiple WSO2 Products via HTTP GET in Admin Services
    35Monitor
  • Later →CVE-2025-13590Feb 19, 2026 · Authenticated arbitrary file upload via a System REST API requiring administrator permission.
    28Monitor

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

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-915233 days apartImproper Privilege Management in Multiple WSO2 API Manager via keymanager-operations DCR Endpoint
    39Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

  • CVE-2025-1090713 days apartAuthenticated Arbitrary File Upload in Multiple WSO2 Products via SOAP Admin Services Leading to Remote Code Execution
    28Monitor
  • CVE-2025-1109313 days apartArbitrary Code Execution with higher privileged users in Multiple WSO2 Products via Script Mediator Engines (GraalJS and NashornJS)
    28Monitor
  • CVE-2025-312513 days apartAuthenticated Arbitrary File Upload in Multiple WSO2 Products via CarbonAppUploader Admin Service Leading to Remote Code Execution
    28Monitor
  • CVE-2025-535025 days apartSSRF and Reflected XSS Vulnerability in Deprecated Try-It Feature of Multiple WSO2 Products
    19Monitor

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Root cause

A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
// Added for the support teamapp.post("/maintenance/reset", resetDevice);

Fixed

ts
if (config.maintenanceEnabled) {  app.post(    "/maintenance/reset",    requireSession, requireRole("admin"), resetDevice  );}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records