CVE-2025-5569VulnerabilityPublished 4 Jun 2025

CVE-2025-5569: IdeaCMS · SQL Injection

Affects IdeaCMSSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 5.3 Medium · fixed in 1.8 : update IdeaCMS when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.8

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

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

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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jun 2025
Detectable: evidence found.
nuclei template: IdeaCMS <= 1.7 - SQL Injection
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-25.

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

Affected software

Product	Affected	Fixed in
GitHubideacms/ideacms`pkg:github/ideacms/ideacms`Other threats	Affected =1.2 =1.3 =1.4 =1.5 =1.6 =1.7	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately assess their use of IdeaCMS and identify any installations running versions 1.2 through 1.7. The primary mitigation is to upgrade all affected IdeaCMS instances to version 1.8 or later, which contains the official patch. If immediate upgrade is not feasible, organizations should implement web application firewall (WAF) rules to detect and block suspicious SQL injection patterns targeting the 'Field' parameter in the vulnerable endpoint. Additionally, input validation and parameterized queries should be enforced at the application level if custom modifications exist. Regular security audits and vulnerability scanning should be conducted to detect any exploitation attempts. Monitoring logs for unusual database query patterns or error messages related to SQL injection attempts can provide early warning signs. Finally, organizations should ensure backups are current and tested to enable recovery in case of data compromise.

Description

A vulnerability was found in IdeaCMS up to 1.7 and classified as critical. This issue affects the function Article/Goods of the file /api/v1.index.article/getList.html. The manipulation of the argument Field leads to sql injection. The attack may be initiated remotely. Upgrading to version 1.8 is able to address this issue. The patch is named 935aceb4c21338633de6d41e13332f7b9db4fa6a. It is recommended to upgrade the affected component.

Impact

For European organizations using IdeaCMS versions 1.2 to 1.7, this vulnerability could allow attackers to execute arbitrary SQL commands remotely, potentially leading to unauthorized data access, data manipulation, or disruption of service. Although the CVSS score suggests medium severity with limited impact, exploitation could still result in leakage of sensitive information or unauthorized changes to website content or backend data. This could damage organizational reputation, violate data protection regulations such as GDPR, and lead to financial or operational consequences. The risk is heightened for organizations hosting critical or sensitive content on IdeaCMS, especially those without timely patch management processes. Since the vulnerability requires no user interaction and no authentication, automated scanning and exploitation attempts could target vulnerable European websites, increasing exposure.

Summary

CVE-2025-5569 is a medium-severity SQL Injection vulnerability affecting IdeaCMS versions 1.2 through 1.7. The flaw exists in the /api/v1.index.article/getList.html endpoint, specifically within the Article/Goods function, where the 'Field' parameter is improperly sanitized. This allows an unauthenticated remote attacker to inject malicious SQL code, potentially manipulating database queries. The vulnerability does not require user interaction and can be exploited over the network without prior authentication, increasing its risk profile. However, the CVSS 4.0 vector indicates a low impact on confidentiality, integrity, and availability, suggesting limited data exposure or modification potential. The vulnerability has been patched in IdeaCMS version 1.8, with the fix identified by commit 935aceb4c21338633de6d41e13332f7b9db4fa6a. There are currently no known exploits in the wild, but the ease of remote exploitation and the common use of CMS platforms for content management make this a relevant threat to organizations using affected versions of IdeaCMS.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Jul 2025, 17:40 UTC

Public exploits and detectiona Nuclei detection template

Technical details

References

Community reviews

Related threats