Security readout for executives and security teams
Plain-English summary
Fooocus 2.5.5 and earlier can treat malicious metadata as executable code. Anyone able to reach the web interface may potentially take control of the hosting instance, affecting its data, integrity, and availability. The supplied sources identify no released patched version.
Executive priority
Prioritize immediately when an affected Fooocus interface is externally or broadly reachable. Isolate exposure now, assign ownership for monitoring vendor updates, and consider suspending the service where restrictions are inadequate. Internal, tightly restricted instances still require prompt remediation planning.
Technical view
CVE-2025-31114 is a CWE-95 code-injection flaw caused by unsafe eval use while processing metadata JSON. A network attacker with web UI access may execute arbitrary code on the Fooocus instance without privileges or user interaction. It carries CVSS 4.0 score 9.3.
Likely exposure
Fooocus deployments running version 2.5.5 or earlier are affected. Risk is greatest where the web UI is internet-accessible or reachable by untrusted users who can cause metadata JSON to be processed. The bundle provides no CPEs or deployment telemetry, so organizational prevalence is unknown.
Exploitation context
The CVE is not listed in CISA KEV, and the supplied sources do not establish active exploitation. Public disclosure and a proposed fix may help defenders understand the flaw, but they also increase awareness. Treat reachable affected instances as urgent despite the absence of confirmed exploitation evidence.
Researcher notes
The key sink is unsafe eval during metadata JSON processing, classified as CWE-95. Successful exploitation may execute code in the Fooocus process context. The CVSS 4.0 vector indicates network reachability, low complexity, no privileges, and no interaction. Available evidence names a proposed fix but no patched release or confirmed in-the-wild exploitation.
Mitigation direction
- Restrict Fooocus web UI access to trusted users and approved network paths.
- Remove internet exposure or disable affected instances when access cannot be adequately restricted.
- Monitor the project for a released, vendor-supported patched version.
- Evaluate the suggested fix pull request cautiously; it is not identified as a released patch.
- Apply the vendor-supported update when available and retest access controls.
Validation and detection
- Inventory Fooocus instances and confirm their installed versions.
- Identify instances running version 2.5.5 or earlier.
- Verify whether each web UI is internet-accessible or reachable by untrusted networks.
- Review access and application logs for unexpected metadata processing or process activity.
- Confirm network restrictions prevent unauthorized users from reaching the interface.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-95: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-31114 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://securitylab.github.com/advisories/GHSL-2024-196_Fooocus/CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/lllyasviel/Fooocus/issues/3552CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/lllyasviel/Fooocus/pull/4207CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.