How severe is CVE-2022-24891?

CVE-2022-24891 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-24891?

CVE-2022-24891 affects the following packages: org.owasp.esapi:esapi (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-24891?

Update org.owasp.esapi:esapi to 2.3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24891 is resolved across your whole dependency graph.

How do I detect CVE-2022-24891 in my Maven dependencies?

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

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

Yes. There are 1 known exploit references for CVE-2022-24891, including 1 in-the-wild exploitation 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-2022-24891?

CVE-2022-24891 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 78th 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-2022-24891?

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

CVE-2022-24891 was published on April 27, 2022 and was last updated on October 28, 2026. 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-2022-24891 — esapi

MEDIUM

CVE-2022-24891 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in org.owasp.esapi:esapi. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.owasp.esapi:esapi — see the affected versions and patch details below.

Cross-site Scripting in org.owasp.esapi:esapi -- antisamy-esapi.xml configuration file

Also known asGHSA-q77q-vx4q-xx6q

Published

Apr 27, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-24891.

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk+0.03%

Lower risk than most CVEs78th percentile — riskier than 78% 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

1 pkg affected

☕org.owasp.esapi:esapi

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

Impact

There is a potential for an XSS vulnerability in ESAPI caused by a incorrect regular expression for "onsiteURL" in the antisamy-esapi.xml configuration file that can cause URLs with the "javascript:" scheme to NOT be sanitized. See the reference below for full details.

Patches

Patched in ESAPI 2.3.0.0 and later. See important remediation details in the reference given below.

Workarounds

Manually edit your antisamy-esapi.xml configuration files to change the "onsiteURL" regular expression as per remediation instructions in the reference below.

References

Security Bulletin 8

For more information

If you have any questions or comments about this advisory:

Email one of the project co-leaders. See email addresses listed on the OWASP ESAPI wiki page, under "Leaders".
Send email to one of the two ESAPI related Google Groups listed under Where to Find More Information on ESAPI on our README.md page.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.owasp.esapi:esapi`	all versions	2.3.0.0`org.owasp.esapi:esapi:2.3.0.0`

Affected Products

4 products · 8 configurations

Application

active iq unified managernetapp

all

Application

oncommand workflow automationnetapp

all

Application

weblogic serveroracle

3 versions

12.2.1.3.012.2.1.4.014.1.1.0.0

Application

enterprise security apiowasp

< 2.3.0.0

range

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.

ESAPI (The OWASP Enterprise Security API) is a free, open source, web ap…

github.comNVDMay 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.owasp.esapi:esapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.owasp.esapi:esapi to 2.3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24891 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

### Impact There is a potential for an XSS vulnerability in ESAPI caused by a incorrect regular expression for "onsiteURL" in the **antisamy-esapi.xml** configuration file that can cause URLs with the "javascript:" scheme to NOT be sanitized. See the reference below for full details. ### Patches Patched in ESAPI 2.3.0.0 and later. See important remediation details in the reference given below. ### Workarounds Manually edit your **antisamy-esapi.xml** configuration files to change the "onsiteURL" regular expression as per remediation instructions in the reference below. ### References [Secur

O3 Security · Impact-Aware SCA

Is CVE-2022-24891 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

OpenSSF Scorecard

Package health score

esapi-java-legacy

4.6/10

Maintained0/10

Code-Review3/10

Branch-ProtectionN/A

Assessed Nov 9, 2026

Timeline

Disclosed

Apr 27, 2022

First exploit

May 9, 2022

Last updated

Oct 28, 2026

Identifiers

CVE-2022-24891

GHSA-q77q-vx4q-xx6q

References

Advisorygithub.com · CVE 2022 24891.json Advisorygithub.com · GHSA q77q vx4q xx6q Advisorynvd.nist.gov · CVE 2022 24891 Advisorysecurity.netapp.com · ntap 20230127 0014 Webgithub.com · ESAPI security bulletin8.pdf Webgithub.com · esapi4java core 2.3.0.0 release notes.txt Weblists.debian.org · msg00010 Weboracle.com · cpujul2022 Websecurity.netapp.com · ntap 20230127 0014 Packagegithub.com · esapi java legacy

Related vulnerabilities

Also affects esapi

This CVE is medium severity; 5 of 6 other CVEs affecting esapi are rated as high or higher (top: high).

GHSA-r68h-jhhj-9jvmGHSA-7c2q-5qmr-v76qCVE-2013-5679CVE-2013-5960CVE-2022-23457CVE-2010-3300

Same weakness: CWE-79

This CVE is medium severity; 1 of 2 other CVEs with CWE-79 is rated as high or higher (top: moderate).

CVE-2026-126075CVE-2026-126063Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-24891 — esapi

Exploitation Status

Proof-of-concept exploit code exists

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Impact

Patches

Workarounds

References

For more information

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2022-24891 in your dependencies?