Skip to main content
CVE-2025-52085VulnerabilityPublished Updated

CVE-2025-52085: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

AI-suggested

1. Immediate mitigation should include restricting access to the vulnerable API endpoint to trusted users and networks only, using network segmentation and firewall rules. 2. Enforce strong authentication mechanisms and monitor for unusual login activities to detect potential credential compromise. 3. Implement input validation and parameterized queries or prepared statements in the backend API to prevent SQL injection. 4. Conduct thorough code reviews and security testing of the Yoosee application, focusing on API endpoints handling database queries. 5. Apply principle of least privilege to database users to limit the scope of data accessible even if SQL injection occurs. 6. Monitor database logs for suspicious queries or anomalies indicative of injection attempts. 7. If patches become available, prioritize immediate deployment. 8. Educate users and administrators about the risks of credential sharing and phishing attacks that could lead to authentication compromise. 9. Consider deploying Web Application Firewalls (WAF) with SQL injection detection rules tailored to the Yoosee application traffic patterns.

Description

An SQL injection vulnerability in Yoosee application v6.32.4 allows authenticated users to inject arbitrary SQL queries via a request to a backend API endpoint. Successful exploitation enables extraction of sensitive database information, including but not limited to, the database server banner and version, current database user and schema, the current DBMS user privileges, and arbitrary data from any table.

References

Community reviews

Loading reviews…