CVE-2018-1999023

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.

Published: 2018-07-23 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-1999023 is rated Moderate Risk (62.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.72%). EPSS rose +1.28% over the last day, indicating growing attacker interest. Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2018-1999023

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.45% 1.72% +1.28%
2 2025-11-21 0.80% 0.45% -0.35%
3 2025-11-18 — 0.80% —

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-1999023

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2018-1999023

OS Trackers for CVE-2018-1999023

vendor priority summary link
debian not yet assigned CVE-2018-1999023 not yet assigned priority: Debian including 1 source packages (wesnoth-1.14), 1 status rows across 1 suites (bullseye): resolved 1. https://security-tracker.debian.org/tracker/CVE-2018-1999023
ubuntu medium CVE-2018-1999023 medium priority: Ubuntu including 3 source packages (wesnoth-1.10, wesnoth-1.12, wesnoth-1.14), 51 status rows across 17 suites (bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 39, not-affected 7, released 3, needed 2. https://ubuntu.com/security/CVE-2018-1999023

Affected software / configurations for CVE-2018-1999023

Vendor Product Version Raw CPE
wesnoth the_battle_for_wesnoth >= 1.7.0, <= 1.14.3 cpe:2.3:a:wesnoth:the_battle_for_wesnoth:*:*:*:*:*:*:*:*

References for CVE-2018-1999023

cvelogic Threat Intelligence