Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA WSO2

CVE-2025-14260: Server Side Request Forgery in Multiple WSO2 Products Allows Access to Internal and External Resources

Noroxi assessment

Priority: Monitor (action score 33/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • 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

Due to the improper implementation of access control rules, the WSO2 product accepts user-supplied input related to resource location without enforcing expected validation constraints. This can be exploited by an unauthenticated actor to direct the server to make requests to arbitrary network locations. Exploiting this vulnerability allows a malicious actor to access both internal and external resources, available through the network or filesystem, that are reachable by the WSO2 product. This could potentially lead to unauthorized access to sensitive data and systems.

HighCVSS 8.3 · v3.1—No exploit No fix recorded
Published
Oct 28, 2026
Updated
Oct 29, 2026
EPSS
—

Report tools

JSON

Action score

33

Monitor

Low priority for now.

CVSS
33 / 40 · 8.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · —

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · WSO2
8.3
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-14260

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for wso2 records

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.

—

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 SAML2 SSO Authenticator UI Bundle

    • 5.5.0 and later · before 5.5.0.2affected
    • 5.5.2 and later · before 5.5.2.5affected
    • 5.5.9 and later · before 5.5.9.4affected
    • 5.5.10 and later · before 5.5.10.1affected
    • 5.6.4 and later · before 5.6.4.1affected
    • 5.7.2 and later · before 5.7.2.1affected
    • 5.8.3 and later · before 5.8.3.1affected
    • 5.8.7 and later · before 5.8.7.2affected
    • 5.9.4 and later · before 5.9.4.2affected
    • 5.9.9 and laternot affected

  • WSO2 WSO2 API Manager

    • before 3.1.0unknown
    • 3.1.0 and later · before 3.1.0.354affected
    • 3.2.0 and later · before 3.2.0.458affected
    • 3.2.1 and later · before 3.2.1.99affected
    • 4.0.0 and later · before 4.0.0.379affected
    • 4.1.0 and later · before 4.1.0.265affected
    • 4.2.0 and later · before 4.2.0.205affected
    • 4.3.0 and later · before 4.3.0.115affected
    • 4.4.0 and later · before 4.4.0.79affected

  • WSO2 WSO2 Carbon UI

    • 4.6.0 and later · before 4.6.0.2300affected
    • 4.6.1 and later · before 4.6.1.165affected
    • 4.6.3 and later · before 4.6.3.46affected
    • 4.6.4 and later · before 4.6.4.28affected
    • 4.7.1 and later · before 4.7.1.79affected
    • 4.8.1 and later · before 4.8.1.50affected
    • 4.9.0 and later · before 4.9.0.107affected
    • 4.9.26 and later · before 4.9.26.37affected
    • 4.9.27 and later · before 4.9.27.24affected
    • 4.10.9 and later · before 4.10.9.77affected

  • WSO2 WSO2 Identity Server

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.383affected
    • 5.11.0 and later · before 5.11.0.430affected
    • 6.0.0 and later · before 6.0.0.256affected
    • 6.1.0 and later · before 6.1.0.257affected
    • 7.0.0 and later · before 7.0.0.134affected

  • WSO2 WSO2 Identity Server as Key Manager

    • before 5.10.0unknown
    • 5.10.0 and later · before 5.10.0.374affected

  • WSO2 WSO2 Open Banking AM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.403affected

  • WSO2 WSO2 Open Banking IAM

    • before 2.0.0unknown
    • 2.0.0 and later · before 2.0.0.423affected

Same product

wso2: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-14561Access Control Bypass via Publisher REST APIs in Multiple WSO2 Products Allows Cross-Tenant Operations
    36Monitor
  • CVE-2026-3418Arbitrary File Upload via System REST API in Multiple WSO2 Products Allows Remote Code Execution
    36Monitor
  • CVE-2026-3415XML External Entity (XXE) Injection via Schema Validation in Multiple WSO2 Products Allows File Reading and Denial of Service
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2024-6423Oct 21, 2026 · Sensitive Data Exposure via URL Parameters in Multiple WSO2 Products Allows Confidential Information Leakage
    16Monitor
  • ← EarlierCVE-2024-7478Oct 21, 2026 · Username Enumeration via External User Stores in Multiple WSO2 Products Allows User Account Discovery
    23Monitor
  • Later →CVE-2026-11854Oct 28, 2026 · Cross-Site Scripting via Authentication Endpoint Error Message in Multiple WSO2 Products
    24Monitor

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.

Credits

All researchers

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

Variant candidates

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

No nightly-computed relations.

Chain candidates

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

—

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.
  • A low-privileged account is enough.
  • 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
low · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
Low

Weakness class (CWE)

CWE-918 · Server-Side Request Forgery (SSRF)

CVSS vector

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

nvd-secondary

Attack context

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

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → none
  2. Exploit maturity— → none

For records you follow, these changes also arrive as notifications. →

References

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

All records