LiquidFiles < 4.2 - User Enumeration via Password Reset

highseverity

7.3CVSS score

0.8%likelihood of exploitation, next 30 days

56%of all CVEs are less likely

Readycheck to confirm it

LiquidFiles filetransfer server before 4.2 contains a user enumeration vulnerability caused by distinguishable responses in password reset functionality, letting unauthenticated attackers enumerate valid user accounts, exploit requires no authentication.

Impact

Attackers can enumerate valid user emails, increasing risk of targeted password attacks and account compromise.

Fix

Update to version 4.2 or later which introduces user-based lockout mechanisms.

How to confirm it

Send: POST /password_reset
Positive when: contains(set_cookie, '_filetransfer_session') and status_code == 302
Send: GET /
Positive when: contains_all(body, 'invalid_email','LiquidFiles') and status_code == 200

Run it with nuclei: nuclei -id CVE-2025-56132 -u <target>

The full check

id: CVE-2025-56132

info:
  name: LiquidFiles < 4.2 - User Enumeration via Password Reset
  author: DhiyaneshDk
  severity: high
  description: |
    LiquidFiles filetransfer server before 4.2 contains a user enumeration vulnerability caused by distinguishable responses in password reset functionality, letting unauthenticated attackers enumerate valid user accounts, exploit requires no authentication.
  impact: |
    Attackers can enumerate valid user emails, increasing risk of targeted password attacks and account compromise.
  remediation: |
    Update to version 4.2 or later which introduces user-based lockout mechanisms.
  reference:
    - https://nvd.nist.gov/vuln/detail/CVE-2025-56132
    - https://docs.liquidfiles.com/release_notes/version_4-2-x.html
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
    cvss-score: 7.3
    cve-id: CVE-2025-56132
    cwe-id: CWE-305
    epss-score: 0.00768
    epss-percentile: 0.55868
  metadata:
    verified: true
    max-request: 2
    vendor: liquidfiles
    product: liquidfiles
    shodan-query: http.title:"LiquidFiles"
    fofa-query: title="LiquidFiles"
  tags: cve,cve2025,liquidfiles,user-enum,vkev,vuln

flow: http(1) && http(2)

variables:
  email: "nonexistent-user-enumtest-{{rand_int(10000,99999)}}@test.invalid"

http:
  - raw:
      - |
        POST /password_reset HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/x-www-form-urlencoded

        user[email]={{email}}

    matchers:
      - type: dsl
        dsl:
          - "contains(set_cookie, '_filetransfer_session')"
          - "status_code == 302"
        condition: and
        internal: true

  - raw:
      - |
        GET / HTTP/1.1
        Host: {{Hostname}}

    matchers:
      - type: dsl
        dsl:
          - "contains_all(body, 'invalid_email','LiquidFiles')"
          - "status_code == 200"
        condition: and

References

Use this check only on systems you are authorised to test. Where the data comes from