CVE-2018-1000632: dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element

This week

HIGH 7.5REMOTEWATCHLISTUPGRADEMITIGATEDOWNGRADE

CVE-2018-1000632 is a high-severity flaw (CVSS 7.5) affecting dom4j, debian linux, flexcube investor servicing. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.

Why this priority

High severity
EPSS top 6%: very likely to be exploited
Public exploit reference
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	6.6% (top 6%)
CISA exploited list	No
Weakness	CWE-91
Published	2018-08-20
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: debian · dom4j project · oracle

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-08-20 19:31 UTCPublished CVE record published
2026-06-17 01:32 UTCUpdated Record last modified

dom4j project dom4j UPGRADE

Affected: >= 2.0.0 and < 2.0.3 · >= 2.1.0 and < 2.1.1

Fixed in: 2.0.3, 2.1.1

Safe to downgrade to: a release before 2.0.0

1. Check installed version

apt-cache policy dom4j || rpm -q dom4j || dom4j --version

2. UPGRADE to 2.0.3 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dom4j

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dom4j

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.0 (Debian / Ubuntu)

apt-cache madison dom4j sudo apt install dom4j=<VERSION_BEFORE_2.0.0> sudo apt-mark hold dom4j

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list dom4j sudo dnf downgrade dom4j-<VERSION_BEFORE_2.0.0> sudo dnf versionlock add dom4j

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

debian debian linux MITIGATE

Affected: 8.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

oracle flexcube investor servicing DOWNGRADE

Affected: 12.0.4 · 12.1.0 · 12.3.0 · 12.4.0 · 14.0.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 12.0.4

1. Check installed version

apt-cache policy flexcube-investor-servicing || rpm -q flexcube-investor-servicing || flexcube-investor-servicing --version

2. No fixed release: DOWNGRADE to a release before 12.0.4 (Debian / Ubuntu)

apt-cache madison flexcube-investor-servicing sudo apt install flexcube-investor-servicing=<VERSION_BEFORE_12.0.4> sudo apt-mark hold flexcube-investor-servicing

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list flexcube-investor-servicing sudo dnf downgrade flexcube-investor-servicing-<VERSION_BEFORE_12.0.4> sudo dnf versionlock add flexcube-investor-servicing

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

oracle primavera p6 enterprise project portfolio management UPGRADE

Affected: >= 16.1.0.0 and <= 16.2.20.1 · >= 17.1.0.0 and <= 17.12.17.1 · >= 18.1.0.0 and <= 18.8.19.0 · >= 19.12.0.0 and <= 19.12.6.0

Fixed in: newer than 19.12.6.0

Safe to downgrade to: a release before 16.1.0.0

1. Check installed version

apt-cache policy primavera-p6-enterprise-project-portfolio-management || rpm -q primavera-p6-enterprise-project-portfolio-management || primavera-p6-enterprise-project-portfolio-management --version

2. UPGRADE to newer than 19.12.6.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade primavera-p6-enterprise-project-portfolio-management

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade primavera-p6-enterprise-project-portfolio-management

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 16.1.0.0 (Debian / Ubuntu)

apt-cache madison primavera-p6-enterprise-project-portfolio-management sudo apt install primavera-p6-enterprise-project-portfolio-management=<VERSION_BEFORE_16.1.0.0> sudo apt-mark hold primavera-p6-enterprise-project-portfolio-management

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list primavera-p6-enterprise-project-portfolio-management sudo dnf downgrade primavera-p6-enterprise-project-portfolio-management-<VERSION_BEFORE_16.1.0.0> sudo dnf versionlock add primavera-p6-enterprise-project-portfolio-management

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

oracle rapid planning DOWNGRADE

Affected: 12.1 · 12.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 12.1

1. Check installed version

apt-cache policy rapid-planning || rpm -q rapid-planning || rapid-planning --version

2. No fixed release: DOWNGRADE to a release before 12.1 (Debian / Ubuntu)

apt-cache madison rapid-planning sudo apt install rapid-planning=<VERSION_BEFORE_12.1> sudo apt-mark hold rapid-planning

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list rapid-planning sudo dnf downgrade rapid-planning-<VERSION_BEFORE_12.1> sudo dnf versionlock add rapid-planning

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

oracle retail integration bus DOWNGRADE

Affected: 15.0 · 16.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 15.0

1. Check installed version

apt-cache policy retail-integration-bus || rpm -q retail-integration-bus || retail-integration-bus --version

2. No fixed release: DOWNGRADE to a release before 15.0 (Debian / Ubuntu)

apt-cache madison retail-integration-bus sudo apt install retail-integration-bus=<VERSION_BEFORE_15.0> sudo apt-mark hold retail-integration-bus

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list retail-integration-bus sudo dnf downgrade retail-integration-bus-<VERSION_BEFORE_15.0> sudo dnf versionlock add retail-integration-bus

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-1000632?

dom4j: upgrade to 2.0.3, 2.1.1; debian linux: mitigate or apply the listed mitigation; flexcube investor servicing: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-1000632 being exploited?

CVE-2018-1000632 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-1000632 affect?

CVE-2018-1000632 affects dom4j, debian linux, flexcube investor servicing. Severity is high (CVSS 7.5). dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear t

How urgent is CVE-2018-1000632?

Priority 65/100. High severity; EPSS top 6%: very likely to be exploited; Public exploit reference; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Debian vulnerabilities

Related CVEs

CVE-2020-10683 CRITICAL 9.8 UPGRADE DOWNGRADE dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might e

References

← Back to latest CVEs