Skip to content

Vendor

wesnoth vulnerabilities

10 published CVES affecting wesnoth, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
10
Critical
0
High
5
Medium
4
Low
1
Unscored
0
CISA KEV
0
Atom feed of wesnoth alerts

Products

Latest wesnoth CVEs

Newest publication first

  1. HighCVSS 8.8 EPSS 1.7%

    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,...

  2. LowCVSS 3.1 EPSS 1.4%

    The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.4 and 1.13.x before 1.13.1, when a case-insensitive filesystem is used, allow remote attackers to obtain sensitive information...

  3. MediumCVSS 4.3 EPSS 1.7%

    The (1) filesystem::get_wml_location function in filesystem.cpp and (2) is_legal_file function in filesystem_boost.cpp in Battle for Wesnoth before 1.12.3 and 1.13.x before 1.13.1 allow remote attackers to obtain sensitive information via vectors related to inclusion of .pbl file...

  4. HighCVSS 9.3 EPSS 10.9%

    The Python AI module in Wesnoth 1.4.x and 1.5 before 1.5.11 allows remote attackers to escape the sandbox and execute arbitrary code by using a whitelisted module that imports an unsafe module, then using a hierarchical module name to access the unsafe module through the whitelis...

  5. HighCVSS 7.5 EPSS 1.5%

    Unspecified vulnerability in Wesnoth 1.2.x before 1.2.8, and 1.3.x before 1.3.12, allows attackers to cause a denial of service (hang) via a "faulty add-on" and possibly execute other commands via unknown vectors related to the turn_cmd option.

  6. HighCVSS 7.8 EPSS 2.1%

    The multiplayer engine in Wesnoth 1.2.x before 1.2.7 and 1.3.x before 1.3.9 allows remote servers to cause a denial of service (crash) via a long message with multibyte characters that can produce an invalid UTF-8 string after it is truncated, which triggers an uncaught exception...

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.