How severe is CVE-2016-4316?

CVE-2016-4316 has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

How do I fix CVE-2016-4316?

The records we use list no patched version of org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui for CVE-2016-4316. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2016-4316 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2016-4316 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2016-4316 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2016-4316, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-4316?

CVE-2016-4316 has an EPSS (Exploit Prediction Scoring System) score of 4.0%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2016-4316?

CVE-2016-4316 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2016-4316 published, and has it been updated?

CVE-2016-4316 was published on May 14, 2022 and was last updated on April 22, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2016-4316 — org.wso2.carbon.ndatasour…

MEDIUM

CVE-2016-4316 is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

WSO2 Carbon vulnerable to Cross-site Scripting

Published

May 14, 2022

Updated

Apr 22, 2025

Affected

3 pkgs

Patched

See advisory

Exploits

4 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

4.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui☕org.wso2.carbon.identity.framework:org.wso2.carbon.identity.mgt.ui☕org.wso2.carbon.commons:org.wso2.carbon.messageflows.ui

Real-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

Multiple cross-site scripting (XSS) vulnerabilities in WSO2 Carbon 4.4.5 allow remote attackers to inject arbitrary web script or HTML via the (1) setName parameter to identity-mgt/challenges-mgt.jsp; the (2) webappType or (3) httpPort parameter to webapp-list/webapp_info.jsp; the (4) dsName or (5) description parameter to ndatasource/newdatasource.jsp; the (6) phase parameter to viewflows/handlers.jsp; or the (7) url parameter to ndatasource/validateconnection-ajaxprocessor.jsp.

Affected Packages

3 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui`	all versions	No fix
☕Maven	`org.wso2.carbon.identity.framework:org.wso2.carbon.identity.mgt.ui`	all versions	No fix
☕Maven	`org.wso2.carbon.commons:org.wso2.carbon.messageflows.ui`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

carbonwso2

1 version

4.4.5

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-40241webappsjsp✓ Verified

WSO2 Carbon 4.4.5 - Persistent Cross-Site Scripting

by hyp3rlinx · Aug 16, 2016

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.wso2.carbon.commons:org.wso2.carbon.ndatasource.ui for CVE-2016-4316. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2016-4316 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 4 public proof-of-concept references are listed on this page.

Timeline

First exploit

Aug 16, 2016

Disclosed

May 14, 2022

Last updated

Apr 22, 2025

Identifiers

CVE-2016-4316

References

Advisorynvd.nist.gov · CVE 2016 4316 Webweb.archive.org · threaded Webexploit-db.com Webhyp3rlinx.altervista.org · WSO2 CARBON v4.4.5 PERSISTENT XSS COOKIE THEFT.txt Webpacketstormsecurity.com · WSO2 Carbon 4.4.5 Cross Site Scripting

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs with CWE-79 are rated as high or higher (top: critical).

CVE-2026-55649CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251CVE-2026-118253Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedApr 22, 2025