What is the CVSS score of CVE-2025-46094?

CVE-2025-46094 has a CVSS 3.1 base score of 3.8 (Low). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N. EPSS exploitation probability: 0.1%.

Which versions of Liquidfiles are affected by CVE-2025-46094?

CVE-2025-46094 is a low-severity vulnerability in LiquidFiles before 4.1.2 (CVSS 3.8).

Is there a public PoC exploit available for CVE-2025-46094?

Yes, a public proof-of-concept exploit is available for CVE-2025-46094. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2025-46094?

During next maintenance window: Apply vendor patches when convenient. Monitor vendor channels for updates.

Liquidfiles CVE-2025-46094

LOW

Path Traversal: '../filedir' (CWE-24)

2025-08-04 cve@mitre.org

Path Traversal Liquidfiles

3.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

3.8 LOW

AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 19:05 vuln.today

PoC Detected

Aug 07, 2025 - 14:30 vuln.today

Public exploit code

CVE Published

Aug 04, 2025 - 23:15 nvd

LOW 3.8

DescriptionCVE.org

LiquidFiles before 4.1.2 allows directory traversal by configuring the pathname of a local executable file as an Actionscript.

AnalysisAI

LiquidFiles before 4.1.2 allows directory traversal by configuring the pathname of a local executable file as an Actionscript. Rated low severity (CVSS 3.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified under CWE-24. LiquidFiles before 4.1.2 allows directory traversal by configuring the pathname of a local executable file as an Actionscript. Affected products include: Liquidfiles. Version information: before 4.1.2.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Apply vendor patches when available. Implement network segmentation and monitoring as interim mitigations.