CVE-2025-7936VulnerabilityPublished 21 Jul 2025

CVE-2025-7936: fuyang_lipengjun platform · SQL Injection

Affects fuyang_lipengjun platformSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Immediate code review and sanitization: Developers should audit the queryPage function and ensure that all inputs, especially 'beanName' and 'methodName', are properly sanitized and validated against a whitelist of allowed values. 2. Use of parameterized queries or prepared statements: Refactor the affected SQL queries to use parameterized queries to prevent injection. 3. Implement Web Application Firewalls (WAF): Deploy WAFs with rules to detect and block SQL Injection attempts targeting the affected endpoints. 4. Monitor logs and network traffic: Set up enhanced monitoring to detect unusual query patterns or spikes in errors related to ScheduleJobLogController endpoints. 5. Accelerate patching: Engage with the vendor or development team to obtain and deploy patches or mitigations as soon as they become available, despite the rolling release model. 6. Restrict access: Where possible, limit network exposure of the vulnerable service to trusted networks or VPNs to reduce attack surface. 7. Conduct penetration testing: Perform targeted security testing to verify the effectiveness of mitigations and detect any residual vulnerabilities. 8. Educate developers and administrators on secure coding practices to prevent similar issues in future releases.

Description

A vulnerability has been found in fuyang_lipengjun platform up to ca9aceff6902feb7b0b6bf510842aea88430796a and classified as critical. Affected by this vulnerability is the function queryPage of the file com/platform/controller/ScheduleJobLogController.java. The manipulation of the argument beanName/methodName leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available.

Impact

For European organizations using the fuyang_lipengjun platform, this vulnerability poses a risk of unauthorized access to sensitive data stored in backend databases, potential data corruption, and service disruption. The ability to execute arbitrary SQL commands remotely without authentication could lead to data breaches, loss of data integrity, and denial of service conditions. This is particularly concerning for organizations handling personal data under GDPR, as exploitation could result in regulatory penalties and reputational damage. The medium CVSS score reflects a moderate risk, but the critical nature of SQL Injection vulnerabilities means that even moderate vulnerabilities can escalate if chained with other weaknesses. The rolling release nature of the platform may delay patch deployment, increasing exposure time. European entities in sectors such as finance, healthcare, and public administration, which often rely on robust data integrity and confidentiality, could face significant operational and compliance impacts if this vulnerability is exploited.

Summary

CVE-2025-7936 is a critical SQL Injection vulnerability identified in the fuyang_lipengjun platform, specifically affecting the function queryPage within the ScheduleJobLogController.java file. The vulnerability arises from improper sanitization or validation of the input parameters 'beanName' and 'methodName', which are directly used in SQL queries. This flaw allows an unauthenticated remote attacker to inject arbitrary SQL commands, potentially leading to unauthorized data access, data modification, or disruption of database operations. The platform uses a rolling release model, which complicates precise version tracking for affected and patched releases. The vulnerability has a CVSS 4.0 base score of 5.3 (medium severity), with attack vector being network-based and no user interaction required. The exploit has been publicly disclosed but no known active exploitation in the wild has been reported yet. The vulnerability impacts confidentiality, integrity, and availability to a limited extent due to partial impact metrics (low confidentiality, integrity, and availability impacts). The attack requires no authentication and can be performed remotely, increasing the risk profile. However, the partial impact scores and lack of known exploits suggest moderate risk at present. The vulnerability is significant because SQL Injection remains one of the most dangerous web application vulnerabilities, often leading to severe breaches if exploited effectively. Given the public disclosure, organizations using this platform should prioritize remediation to prevent potential exploitation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 21 Jul 2025, 20:01 UTC

Technical details

References

Community reviews

Related threats