CVE-2024-58249

In wxWidgets before 3.2.7, a crash can be triggered in wxWidgets apps when connections are refused in wxWebRequestCURL.

Published: 2025-04-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-58249 is rated Low Risk (22.8/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.08%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

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-2024-58249

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-05-26 0.28% 0.08% -0.20%
2 2026-02-10 0.06% 0.28% +0.23%
3 2025-12-20 — 0.06% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-58249

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.7 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.2 1.4 [email protected]

Weakness enumeration for CVE-2024-58249

OS Trackers for CVE-2024-58249

vendor priority summary link
alpine low CVE-2024-58249: 1 source package rows (wxwidgets); 4 state rows across 2 repos (3.22-community, edge-community); fixed 0, open 4. https://security.alpinelinux.org/vuln/CVE-2024-58249
debian not yet assigned CVE-2024-58249 not yet assigned priority: Debian including 1 source packages (wxwidgets3.2), 4 status rows across 4 suites (bookworm, forky, sid, trixie): resolved 3, open 1. https://security-tracker.debian.org/tracker/CVE-2024-58249
suse medium CVE-2024-58249 severity moderate: SUSE including 136 source package names (libwx_base-suse-devel-3.1.5-150400.3.10.1, libwx_base-suse-nostl-devel-3.1.5-150400.3.10.1, …), 291 product×package rows across 28 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (28 product lines)): Known Not Affected 154, Fixed 137. https://www.suse.com/security/cve/CVE-2024-58249/
ubuntu medium CVE-2024-58249 medium priority: Ubuntu including 1 source packages (wxwidgets3.2), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): DNE 2, ignored 2, needs-triage 2, released 1. https://ubuntu.com/security/CVE-2024-58249

Affected software / configurations for CVE-2024-58249

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2024-58249

cvelogic Threat Intelligence