Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-4760: An authenticated stored cross-site scripting (XSS) vulnerability exists in multiple WSO2 products due to impro

19
Routine
MEDIUM 4.8DOWNGRADEDOWNGRADEDOWNGRADE

CVE-2025-4760 is a medium-severity flaw (CVSS 4.8) affecting api control plane, api manager, traffic manager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An authenticated stored cross-site scripting (XSS) vulnerability exists in multiple WSO2 products due to improper validation of user-supplied input during API document upload in the Publisher portal. A user with publisher privileges can upload a crafted API document containing malicious JavaScript, which is later rendered in the browser when accessed by other users. A successful attack could result in redirection to malicious websites, unauthori

Why this priority

  • No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score4.8 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionRequired
EPSS exploit chance0.2% (top 92%)
CISA exploited listNo
WeaknessCWE-79
Published2025-09-23
Last modified2026-10-18
Publisher (CNA): WSO2 LLC · Vendor: wso2

Share: LinkedIn · X · Reddit

Last updated 2026-10-18 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

wso2 api control plane DOWNGRADE
Affected: 4.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy api-control-plane || rpm -q api-control-plane || api-control-plane --version
2. No fixed release: DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison api-control-plane sudo apt install api-control-plane=<VERSION_BEFORE_4.5.0> sudo apt-mark hold api-control-plane
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-control-plane sudo dnf downgrade api-control-plane-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add api-control-plane
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 api manager DOWNGRADE
Affected: 3.2.0 · 3.2.1 · 4.1.0 · 4.2.0 · 4.3.0 · 4.4.0 · 4.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 3.2.0
1. Check installed version
apt-cache policy api-manager || rpm -q api-manager || api-manager --version
2. No fixed release: DOWNGRADE to a release before 3.2.0 (Debian / Ubuntu)
apt-cache madison api-manager sudo apt install api-manager=<VERSION_BEFORE_3.2.0> sudo apt-mark hold api-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list api-manager sudo dnf downgrade api-manager-<VERSION_BEFORE_3.2.0> sudo dnf versionlock add api-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 traffic manager DOWNGRADE
Affected: 4.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy traffic-manager || rpm -q traffic-manager || traffic-manager --version
2. No fixed release: DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison traffic-manager sudo apt install traffic-manager=<VERSION_BEFORE_4.5.0> sudo apt-mark hold traffic-manager
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list traffic-manager sudo dnf downgrade traffic-manager-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add traffic-manager
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
wso2 universal gateway DOWNGRADE
Affected: 4.5.0
Fixed in: no fixed release known
Safe to downgrade to: a release before 4.5.0
1. Check installed version
apt-cache policy universal-gateway || rpm -q universal-gateway || universal-gateway --version
2. No fixed release: DOWNGRADE to a release before 4.5.0 (Debian / Ubuntu)
apt-cache madison universal-gateway sudo apt install universal-gateway=<VERSION_BEFORE_4.5.0> sudo apt-mark hold universal-gateway
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list universal-gateway sudo dnf downgrade universal-gateway-<VERSION_BEFORE_4.5.0> sudo dnf versionlock add universal-gateway
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-4760?

api control plane: downgrade or apply the listed mitigation; api manager: downgrade or apply the listed mitigation; traffic manager: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-4760 being exploited?

CVE-2025-4760 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-4760 affect?

CVE-2025-4760 affects api control plane, api manager, traffic manager. Severity is medium (CVSS 4.8). An authenticated stored cross-site scripting (XSS) vulnerability exists in multiple WSO2 products due to improper validation of user-supplied input during API document upload in the Publisher portal. A user with publisher privileges can upl

How urgent is CVE-2025-4760?

Priority 19/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.