CVE-2025-7568
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-07-14

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in qianfox FoxCMS up to 1.2.5. It has been classified as critical. Affected is the function batchCope of the file app/admin/controller/Video.php. The manipulation of the argument ids leads to sql injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-07-14
Last Modified
2026-04-29
Generated
2026-05-27
AI Q&A
2025-07-14
EPSS Evaluated
2026-05-26
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
qianfox foxcms to 1.2.5 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2025-7568 is a critical SQL injection vulnerability in qianfox FoxCMS versions up to 1.2.5. It exists in the batchCope function of the app/admin/controller/Video.php file. The vulnerability arises because the ids argument is improperly handled, allowing an attacker to inject malicious SQL code. This can be exploited remotely without authentication, potentially giving the attacker unauthorized access to or manipulation of the database. [1, 2]


How can this vulnerability impact me? :

This vulnerability can impact you by allowing attackers to remotely execute arbitrary SQL commands on your FoxCMS database. This can lead to unauthorized access, data leakage, data modification, or disruption of service, affecting the confidentiality, integrity, and availability of your system. [2]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability can negatively affect compliance with standards like GDPR and HIPAA because it risks unauthorized access to sensitive data, potentially leading to data breaches. Such breaches can result in violations of data protection and privacy regulations, exposing organizations to legal and financial penalties. [2]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by identifying the presence of the vulnerable FoxCMS version (up to 1.2.5) and specifically the file app/admin/controller/Video.php. One suggested method is using Google dorking with queries such as `inurl:app/admin/controller/Video.php` to find exposed instances. Additionally, monitoring for unusual or suspicious SQL injection attempts targeting the `ids` parameter in the batchCope function could help detect exploitation attempts. Specific commands are not provided, but network monitoring tools or web application scanners that detect SQL injection attempts on this endpoint could be used. [2]


What immediate steps should I take to mitigate this vulnerability?

No known mitigations or countermeasures have been published for this vulnerability. The suggested immediate step is to replace the affected FoxCMS software (version up to 1.2.5) with an alternative product. Since the vendor did not respond and no patches are available, removing or isolating the vulnerable system and restricting access to the administrative backend could also help reduce risk. [2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart