CVE-2025-5431VulnerabilityPublished 2 Jun 2025

CVE-2025-5431: 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, 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 39% 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 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

Affected software

Product	Affected	Fixed in
AssamLook CMS	Affected =1.0	Fixed in–

AI-suggested

1. Immediate mitigation should include implementing web application firewall (WAF) rules to detect and block SQL Injection attempts targeting the 'ID' parameter in /department-profile.php. 2. Conduct thorough input validation and sanitization on all user-supplied inputs, especially the 'ID' parameter, using parameterized queries or prepared statements if possible. 3. If source code access is available, review and refactor the vulnerable function to eliminate direct concatenation of user input into SQL queries. 4. Monitor web server and application logs for suspicious query patterns or anomalous access attempts related to the vulnerable endpoint. 5. Restrict database user privileges to the minimum necessary to limit the impact of a successful injection. 6. Consider isolating or temporarily disabling the affected functionality if feasible until a vendor patch or official fix is released. 7. Engage with the vendor or community to seek updates or patches and stay informed about any emerging exploits. 8. Implement network-level segmentation and intrusion detection systems to detect lateral movement attempts following exploitation.

Description

A vulnerability, which was classified as critical, was found in AssamLook CMS 1.0. Affected is an unknown function of the file /department-profile.php. The manipulation of the argument ID 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.

Impact

For European organizations using AssamLook CMS 1.0, this vulnerability poses a risk of unauthorized access to sensitive data stored in the CMS database, including potentially confidential departmental information. Although the CVSS score indicates medium severity, the ability to perform SQL Injection remotely without user interaction or authentication means attackers could exploit this flaw to extract or alter data, disrupt services, or pivot to further attacks within the network. The impact is heightened for organizations relying on AssamLook CMS for critical web presence or internal information management. Data breaches resulting from exploitation could lead to regulatory non-compliance under GDPR, reputational damage, and operational disruptions. The lack of vendor patches means organizations must rely on compensating controls to mitigate risk. Given the public disclosure, attackers may develop exploits targeting European entities, especially those with limited cybersecurity maturity or monitoring capabilities.

Summary

CVE-2025-5431 is a SQL Injection vulnerability identified in AssamLook CMS version 1.0, specifically within an unspecified function in the /department-profile.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which allows an attacker to inject malicious SQL code. This injection can be performed remotely without requiring user interaction or authentication, as indicated by the CVSS vector (AV:N/AC:L/AT:N/UI:N/PR:L). The CVSS 4.0 score is 5.3, categorized as medium severity, reflecting limited impact on confidentiality, integrity, and availability (all rated low), and requiring low privileges (PR:L) for exploitation. The absence of known exploits in the wild suggests limited active exploitation currently, but the public disclosure increases the risk of future attacks. The vulnerability could allow attackers to manipulate backend database queries, potentially leading to unauthorized data access or modification, depending on the database schema and application logic. The lack of vendor response and patch availability increases the urgency for organizations using AssamLook CMS 1.0 to implement mitigations.

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