How severe is CVE-2013-3827?

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

Which packages are affected by CVE-2013-3827?

CVE-2013-3827 affects the following packages: org.glassfish:javax.faces (Maven). Ecosystems affected: Maven.

How do I fix CVE-2013-3827?

Update org.glassfish:javax.faces to 2.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-3827 is resolved across your whole dependency graph.

How do I detect CVE-2013-3827 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 CVE-2013-3827 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 CVE-2013-3827?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-3827 can be triaged on real exposure rather than presence alone.

Is CVE-2013-3827 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2013-3827, including 1 documented proof-of-concept exploit on Exploit-DB. 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-2013-3827?

CVE-2013-3827 has an EPSS (Exploit Prediction Scoring System) score of 32.4%, placing it in the 98th 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 warrants monitoring and prompt remediation.

Is there exploit tooling available for CVE-2013-3827?

A Nuclei detection template exists for CVE-2013-3827, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2013-3827 published, and has it been updated?

CVE-2013-3827 was published on May 17, 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-2013-3827 — javax.faces

CVE-2013-3827 is a security vulnerability in org.glassfish:javax.faces. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.glassfish:javax.faces — see the affected versions and patch details below.

Path Traversal in Eclipse Mojarra

Published

May 17, 2022

Updated

Dec 4, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

32.4%probability of exploitation in next 30 days

Moderate Risk0.00%

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

1 pkg affected

☕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

Multiple path traversal flaws where found in Mojarra JSF2 implementation for identifying resources by name or from libraries. An unauthenticated remote attacker can use these flaws to gather otherwise undisclosed information from within an application's root.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.glassfish:javax.faces`	≥ 2.0.0&&< 2.1.19	2.1.19`org.glassfish:javax.faces:2.1.19`

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-38802remotemultiple✓ Verified

Oracle GlassFish Server 2.1.1/3.0.1 - Multiple Subcomponent Resource Identifier Traversal Arbitrary File Access

by Alex Kouzemtchenko · Oct 15, 2013

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.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.1.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-3827 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 CVE-2013-3827 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-3827. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect CVE-2013-3827

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2013-3827 -u https://target

Template: Javafaces LFI
Severity: medium
Impact: Unauthenticated attackers can exploit local file inclusion through Java Server Faces resource handlers to read sensitive configuration files including WEB-INF/web.xml, exposing Oracle GlassFish, WebLogic, and JDeveloper application configurations.
Remediation: Apply the latest patches and updates for the affected software to fix the LFI vulnerability.

Template by ProjectDiscovery nuclei-templates (Random-Robbie), MIT licensed. View the full template. Scan only systems you are authorised to test.

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 HatImportant

RHSA-2014:0029Red Hat JBoss Data Grid 6.2

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-3827 in your dependencies?

O3 Security finds CVE-2013-3827 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