Skip to main content
Menu
CVEs

CVE

FanRuan FineReport unauthenticated file read via resourcepath parameter

Affects FanRuan FineReport 8.0 installations, where unauthenticated attackers can read arbitrary files through the resourcepath parameter. The checked facts name no vendor rating and no fixed version.

CVE-2019-25785Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Do first: Workaround: The checked facts name no workaround. Until a fix is confirmed, limit network access to the ReportServer endpoint so that it is not reachable from untrusted networks.

Summary

FineReport 8.0 contains a path traversal vulnerability that allows unauthenticated attackers to read arbitrary files through the resourcepath parameter of the /WebReport/ReportServer endpoint. Attackers can send GET requests with op=chart and cmd=get_geo_json to read sensitive files like privilege.xml and extract admin credentials. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.

Who should check

Teams running FanRuan FineReport 8.0 with the /WebReport/ReportServer endpoint reachable over the network.

“FineReport 8.0 contains a path traversal vulnerability”

vulncheck.com

cve.now Index

31Pcve.now Index 31 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.7/10CVSS 8.7
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 76 if added to CISA KEV
  • Would score about 71 if CISA's SSVC rates exploitation active
  • Would score about 36 if advisories confirm default setups are exposed

What to do

  • Workaround: The checked facts name no workaround. Until a fix is confirmed, limit network access to the ReportServer endpoint so that it is not reachable from untrusted networks.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2019-25785 (FineReport 8.0 Unauthenticated File Read via ReportServer resourcepath), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2019-25785 (entry last updated 2026-11-18):
Affected:
- FanRuan FineReport: versions 8.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- FanRuan FineReport 8.0 is installed (source: https://www.vulncheck.com/advisories/finereport-8.0-unauthenticated-file-read-via-reportserver-resourcepath)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2019-25785 is not listed as of cve.now's last read.
This KEV status is for CVE-2019-25785 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/finereport/finereport-path-traversal.yaml
- https://www.vulncheck.com/advisories/finereport-8.0-unauthenticated-file-read-via-reportserver-resourcepath
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2019-25785
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2019-25785"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • FanRuan FineReport

    8.0

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2019-25785

Is CVE-2019-25785 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The bug lets unauthenticated attackers read arbitrary files through the resourcepath parameter of ReportServer. The advisory gives privilege.xml as an example, which can be used to extract admin credentials.Source: vulncheck.com

Which versions are affected by CVE-2019-25785?

FineReport: version 8.0.Source: cve.now feed data

Am I affected, and how do I check?

The checked facts name FanRuan FineReport 8.0 as the affected version, with no version range given. To check an installation, look up its installed FineReport version number in the product's version or about information.Source: vulncheck.com

How do I fix CVE-2019-25785?

The checked facts name no fixed version or patch identifier, so no upgrade target is available from them. Check the vendor's advisory for a fix before deciding what to install.Source: vulncheck.com

What if there's no patch?

The checked facts name no workaround. Until a fix is confirmed, limit network access to the ReportServer endpoint so that it is not reachable from untrusted networks.Source: vulncheck.com

More CVEs