How severe is CVE-2021-36737?

No CVSS score has been assigned to CVE-2021-36737 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2021-36737?

CVE-2021-36737 affects the following packages: org.apache.portals.pluto:pluto-portal (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-36737?

Update org.apache.portals.pluto:pluto-portal to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-36737 is resolved across your whole dependency graph.

How do I detect CVE-2021-36737 in my Maven dependencies?

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

How do I mitigate CVE-2021-36737 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-2021-36737 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-36737 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-36737?

CVE-2021-36737 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 83th 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-2021-36737?

CVE-2021-36737 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-2021-36737 published, and has it been updated?

CVE-2021-36737 was published on January 8, 2022 and was last updated on December 4, 2024. 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

CVE-2021-36737 — pluto-portal

CVE-2021-36737 is a Cross-site Scripting (XSS) vulnerability in org.apache.portals.pluto:pluto-portal. A fix is available for org.apache.portals.pluto:pluto-portal — see the affected versions and patch details below.

Cross-site Scripting in Apache Pluto

Published

Jan 8, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.portals.pluto:pluto-portal

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

The input fields of the Apache Pluto UrlTestPortlet are vulnerable to Cross-Site Scripting (XSS) attacks. Users should migrate to version 3.1.1 of the v3-demo-portlet.war artifact

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.portals.pluto:pluto-portal`	all versions	3.1.1`org.apache.portals.pluto:pluto-portal:3.1.1`

Affected Products

1 product · 1 configurations

Application

plutoapache

< 3.1.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.portals.pluto:pluto-portal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.portals.pluto:pluto-portal to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-36737 is resolved across your whole dependency graph.
Workarounds
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

The input fields of the Apache Pluto UrlTestPortlet are vulnerable to Cross-Site Scripting (XSS) attacks. Users should migrate to version 3.1.1 of the v3-demo-portlet.war artifact

O3 Security · Impact-Aware SCA

Is CVE-2021-36737 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works