CVE-2018-1999023: The Battle for Wesnoth Project version 1.7.0 through 1.14.3 contains a Code Injection vulnerability in the Lua

This month

HIGH 8.8UPGRADE

CVE-2018-1999023 is a high-severity flaw (CVSS 8.8) affecting the battle for wesnoth. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Battle for Wesnoth Project version 1.7.0 through 1.14.3 contains a Code Injection vulnerability in the Lua scripting engine that can result in code execution outside the sandbox. This attack appear to be exploitable via Loading specially-crafted saved games, networked games, replays, and player content.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.7% (top 23%)
CISA exploited list	No
Weakness	CWE-94
Published	2018-07-23
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: wesnoth

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

Am I affected?

Timeline

2018-07-23 16:29 UTCPublished CVE record published
2026-06-17 01:48 UTCUpdated Record last modified

wesnoth the battle for wesnoth UPGRADE

Affected: >= 1.7.0 and <= 1.14.3

Fixed in: newer than 1.14.3

Safe to downgrade to: a release before 1.7.0

1. Check installed version

apt-cache policy the-battle-for-wesnoth || rpm -q the-battle-for-wesnoth || the-battle-for-wesnoth --version

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

sudo apt update && sudo apt install --only-upgrade the-battle-for-wesnoth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade the-battle-for-wesnoth

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 1.7.0 (Debian / Ubuntu)

apt-cache madison the-battle-for-wesnoth sudo apt install the-battle-for-wesnoth=<VERSION_BEFORE_1.7.0> sudo apt-mark hold the-battle-for-wesnoth

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

dnf --showduplicates list the-battle-for-wesnoth sudo dnf downgrade the-battle-for-wesnoth-<VERSION_BEFORE_1.7.0> sudo dnf versionlock add the-battle-for-wesnoth

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-1999023?

the battle for wesnoth: upgrade to newer than 1.14.3. Exact commands for each OS are on this page.

Is CVE-2018-1999023 being exploited?

CVE-2018-1999023 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-1999023 affect?

CVE-2018-1999023 affects the battle for wesnoth. Severity is high (CVSS 8.8). The Battle for Wesnoth Project version 1.7.0 through 1.14.3 contains a Code Injection vulnerability in the Lua scripting engine that can result in code execution outside the sandbox. This attack appear to be exploitable via Loading speciall

How urgent is CVE-2018-1999023?

Priority 50/100. High severity

References

← Back to latest CVEs