VulnerabilityPublished 2 Jun 2025

CVE-2025-5430: AssamLook CMS · SQL Injection

Affects AssamLook CMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

5.3Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% 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

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 2 Jun 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
AssamLook CMS	Affected =1.0	Fixed in–

AI-suggested

Given the lack of official patches, European organizations should take immediate steps to mitigate risk: 1) Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection attempts targeting the /product.php endpoint and the 'ID' parameter. 2) Conduct thorough input validation and sanitization on all user-supplied parameters, especially 'ID', using parameterized queries or prepared statements if possible. 3) Restrict database user privileges associated with the CMS to the minimum necessary to limit damage from potential exploitation. 4) Monitor web server and application logs for suspicious activity indicative of SQL Injection attempts. 5) If feasible, isolate or temporarily disable the vulnerable CMS instance until a patch or upgrade is available. 6) Consider migrating to a more secure and actively maintained CMS platform. 7) Educate IT and security teams about this vulnerability and ensure incident response plans include detection and containment strategies for SQL Injection attacks. 8) Regularly back up CMS data and configurations to enable rapid recovery in case of compromise.

Description

A vulnerability, which was classified as critical, has been found in AssamLook CMS 1.0. This issue affects some unknown processing of the file /product.php. The manipulation of the argument ID leads to sql injection. The attack may be initiated 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.

Impact

For European organizations using AssamLook CMS 1.0, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of their web applications and underlying data. Attackers exploiting this SQL Injection could extract sensitive customer or business data, modify product information, or disrupt service availability. This could lead to regulatory compliance violations under GDPR due to unauthorized data disclosure, resulting in legal and financial penalties. Additionally, compromised CMS instances could serve as footholds for further attacks within organizational networks, increasing overall cyber risk. The absence of vendor patches means organizations must rely on alternative mitigations or consider immediate CMS upgrades or replacements. The medium CVSS score may underestimate the real-world impact, especially if the CMS is used to manage critical business functions or sensitive data. The remote and unauthenticated nature of the exploit increases the likelihood of automated scanning and exploitation attempts, particularly targeting publicly accessible web servers.

Summary

CVE-2025-5430 is a SQL Injection vulnerability identified in AssamLook CMS version 1.0, specifically affecting the /product.php file through manipulation of the 'ID' parameter. SQL Injection vulnerabilities occur when untrusted input is improperly sanitized and directly included in SQL queries, allowing attackers to execute arbitrary SQL commands on the backend database. This can lead to unauthorized data access, data modification, or even full system compromise depending on the database privileges. The vulnerability is remotely exploitable without user interaction or authentication, increasing the risk profile. Although the CVSS 4.0 score is 5.3 (medium severity), the description classifies it as critical, indicating potential underestimation of impact. The vendor has not responded to disclosure requests, and no patches or mitigations have been released. No known exploits are currently reported in the wild, but public disclosure increases the likelihood of exploitation attempts. The vulnerability’s impact depends on the database backend and the CMS deployment context, but typical risks include data leakage, data integrity loss, and potential pivoting within the network. The lack of authentication and user interaction requirements makes this vulnerability particularly dangerous for exposed web servers running AssamLook CMS 1.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jul 2025, 12:43 UTC

Technical details

References

Community reviews

Related threats