How severe is GHSA-3m3r-82gc-53mj?

No CVSS score has been assigned to GHSA-3m3r-82gc-53mj yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3m3r-82gc-53mj?

GHSA-3m3r-82gc-53mj affects the following packages: org.glassfish:javax.faces (Maven), org.glassfish:javax.faces (Maven). Ecosystems affected: Maven.

How do I fix GHSA-3m3r-82gc-53mj?

Update org.glassfish:javax.faces to 2.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3m3r-82gc-53mj is resolved across your whole dependency graph.

How do I detect GHSA-3m3r-82gc-53mj in my Maven dependencies?

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

How do I mitigate GHSA-3m3r-82gc-53mj if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3m3r-82gc-53mj?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3m3r-82gc-53mj can be triaged on real exposure rather than presence alone.

Is GHSA-3m3r-82gc-53mj actively exploited in the wild?

No public exploit code has been indexed for GHSA-3m3r-82gc-53mj 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 GHSA-3m3r-82gc-53mj?

GHSA-3m3r-82gc-53mj has an EPSS (Exploit Prediction Scoring System) score of 4.7%, 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 GHSA-3m3r-82gc-53mj?

GHSA-3m3r-82gc-53mj 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 GHSA-3m3r-82gc-53mj published, and has it been updated?

GHSA-3m3r-82gc-53mj was published on May 14, 2022 and was last updated on December 5, 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

GHSA-3m3r-82gc-53mj — javax.faces

GHSA-3m3r-82gc-53mj is a Cross-site Scripting (XSS) vulnerability in org.glassfish:javax.faces. A fix is available for org.glassfish:javax.faces — see the affected versions and patch details below.

Improper Neutralization of Input During Web Page Generation in Mojarra

Also known asCVE-2013-5855

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

4.7%probability of exploitation in next 30 days

Lower Risk0.00%

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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

☕org.glassfish:javax.faces☕org.glassfish:javax.faces

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

Oracle Mojarra 2.2.x before 2.2.6 and 2.1.x before 2.1.28 does not perform appropriate encoding when a (1) <h:outputText> tag or (2) EL expression is used after a scriptor style block, which allows remote attackers to conduct cross-site scripting (XSS) attacks via application-specific vectors.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.glassfish:javax.faces`	≥ 2.2.0&&< 2.2.6	2.2.6`org.glassfish:javax.faces:2.2.6`
☕Maven	`org.glassfish:javax.faces`	≥ 2.1.0&&< 2.1.28	2.1.28`org.glassfish:javax.faces:2.1.28`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.glassfish:javax.faces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.glassfish:javax.faces to 2.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3m3r-82gc-53mj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3m3r-82gc-53mj can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3m3r-82gc-53mj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.0	see advisory	RHSA-2015:0234
Red Hat JBoss BRMS 6.0	see advisory	RHSA-2015:0235
Red Hat JBoss Data Virtualization 6.0	see advisory	RHSA-2015:0765
Red Hat JBoss Data Virtualization 6.1	see advisory	RHSA-2015:0675
Red Hat JBoss Fuse Service Works 6.0	see advisory	RHSA-2015:0720
Red Hat JBoss Operations Network 3.2	see advisory	RHSA-2014:0910
Red Hat JBoss Portal 6.2	`JSF`	RHSA-2015:1009
Red Hat JBoss Web Framework Kit 2.6	`JSF`	RHSA-2014:0896

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-3m3r-82gc-53mj in your dependencies?

O3 Security finds GHSA-3m3r-82gc-53mj across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works