Skip to main content
VulnerabilityPublished Updated

CVE-2024-25081: fontforge · Command Injection

Affects fontforgeSource CVE Database V5

0

Not known to be exploited · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 64% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfontforge/fontforgepkg:github/fontforge/fontforgeOther threatsAffected
  • <=20230101
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-25081, European organizations should implement several specific measures beyond generic advice: 1) Restrict FontForge usage to trusted users and systems, minimizing exposure to untrusted font files. 2) Enforce strict input validation and sanitization on filenames before processing within FontForge or any related workflows. 3) Employ application whitelisting and sandboxing techniques to limit the execution scope of FontForge and contain potential command injection attempts. 4) Monitor local system logs and user activities for unusual command executions or file handling behaviors related to font files. 5) Educate users about the risks of opening font files from untrusted sources and encourage verification of file origins. 6) Maintain up-to-date backups of critical data to recover from potential integrity or availability impacts. 7) Track FontForge updates and apply patches promptly once available. 8) Consider using alternative font editing tools with a stronger security track record if feasible.

Description

Splinefont in FontForge through 20230101 allows command injection via crafted filenames.

References

Community reviews

Loading reviews…