CVE-2025-53964
Goldendict 1.5.0 … 1.5.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:LCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-53964 is a critical-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Goldendict Goldendict. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
GoldenDict versions 1.5.0 and 1.5.1 are affected by CVE-2025-53964, a vulnerability stemming from an exposed dangerous method (CWE-749) that allows arbitrary file reading and modification. The issue is triggered when a user adds a crafted dictionary file and then searches for any term included in that dictionary. Published on 2025-07-17, it carries a CVSS v3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:L).
A remote attacker requires no privileges and can exploit this over the network with low complexity, though user interaction is needed to add the crafted dictionary and initiate a search. Exploitation changes scope and achieves high confidentiality and integrity impacts alongside low availability impact, enabling attackers to read sensitive files and modify arbitrary files on the victim's system.
Mitigation details and patches are referenced in the GoldenDict release notes at https://github.com/goldendict/goldendict/releases, while additional vulnerability information, including likely proof-of-concept details, is available at https://github.com/tigr78/CVE-2025-53964.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-21824
Vulnerability Data
GoldenDict 1.5.0 and 1.5.1 has an exposed dangerous method that allows reading and modifying files when a user adds a crafted dictionary and then searches for any term included in that dictionary.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
V8.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized callers from invoking dangerous API methods or functions.
Least privilege restricts which users or processes may reach dangerous methods, limiting exposure.
Least functionality removes or disables non-essential dangerous methods from the exposed interface altogether.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.
Secure SDLC practices stop developers from exposing dangerous functions in the first place.
Vulnerability identification processes will surface exposed dangerous methods during assessment.
Logical access controls at the network/environment layer can limit reachability of exposed functions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.
Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.
Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.
Secure development life cycle requires removal or protection of dangerous APIs during design and coding.
Application security requirements can mandate that dangerous methods are not exposed in interfaces.
Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Ubuntu 22.04 (3 rules)
- V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
- V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
- V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
- V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749