How severe is CVE-2014-0107?

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

Which packages are affected by CVE-2014-0107?

CVE-2014-0107 affects the following packages: xalan:xalan (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0107?

Update xalan:xalan to 2.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0107 is resolved across your whole dependency graph.

How do I detect CVE-2014-0107 in my Maven dependencies?

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

How do I mitigate CVE-2014-0107 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.

Is CVE-2014-0107 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-0107 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-2014-0107?

CVE-2014-0107 has an EPSS (Exploit Prediction Scoring System) score of 14.1%, placing it in the 97th 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.

What type of vulnerability is CVE-2014-0107?

CVE-2014-0107 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0107 published, and has it been updated?

CVE-2014-0107 was published on April 15, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2014-0107: xalan — Fixed in 2.7.2

EPSS Exploitation Probability

via FIRST.org ↗

14.1%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕xalan:xalan

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 TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`xalan:xalan`	all versions	2.7.2`xalan:xalan:2.7.2`

Affected Products

2 products · 15 configurations

Application

xalan-javaapache

≤ 2.7.1

12 versions

1.0.02.0.02.0.12.1.02.2.02.4.02.4.12.5.02.5.12.5.22.6.02.7.0

Application

webcenter sitesoracle

2 versions

7.6.211.1.1.8.0

Detection & mitigation playbook

Open-source dependency

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

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

Product	Fixed in	Advisory
Fuse ESB Enterprise 7.1.0	see advisory	RHSA-2014:1369
JBoss Enterprise BRMS Platform 5.3	`xalan-j2`	RHSA-2014:1007
Red Hat Enterprise Linux 5	`xalan-j2-0:2.7.0-6jpp.2`	RHSA-2014:0348
Red Hat JBoss A-MQ 6.1	see advisory	RHSA-2014:1351
Red Hat JBoss BPMS 6.0	see advisory	RHSA-2014:0819
Red Hat JBoss BPMS 6.0	`xalan-j2`	RHSA-2014:1291
Red Hat JBoss BRMS 6.0	see advisory	RHSA-2014:0818
Red Hat JBoss BRMS 6.0	`xalan-j2`	RHSA-2014:1290

Frequently Asked Questions

The TransformerFactory in Apache Xalan-Java before 2.7.2 does not properly restrict access to certain properties when FEATURE_SECURE_PROCESSING is enabled, which allows remote attackers to bypass expected restrictions and load arbitrary classes or access external resources via a crafted (1) xalan:content-header, (2) xalan:entities, (3) xslt:content-header, or (4) xslt:entities property, or a Java property that is bound to the XSLT 1.0 system-property function.

O3 Security · Impact-Aware SCA

Is CVE-2014-0107 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2014-0107 — xalan