CVE-2025-5435VulnerabilityPublished 2 Jun 2025

CVE-2025-5435: Marwal Infotech CMS · SQL Injection

Affects Marwal Infotech CMSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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: None
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
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-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
Marwal Infotech CMS	Affected =1.0	Fixed in–

AI-suggested

2) Conduct thorough input validation and sanitization at the application level, if source code access is available, to enforce strict type and format checks on the 'ID' parameter. 3) Restrict database user privileges associated with the CMS to the minimum necessary, avoiding elevated permissions that could exacerbate impact. 4) Monitor web server and database logs for suspicious query patterns or repeated failed attempts indicative of exploitation attempts. 5) Consider isolating or decommissioning vulnerable CMS instances if they are not critical or cannot be secured. 6) Plan for migration to a supported and actively maintained CMS platform with robust security controls. 7) Implement network segmentation to limit access to the CMS backend and database servers. 8) Educate IT and security teams about this vulnerability and ensure incident response plans include steps for SQL injection incidents.

Description

A vulnerability was found in Marwal Infotech CMS 1.0. It has been declared as critical. This vulnerability affects unknown code of the file /page.php. The manipulation of the argument ID leads to sql injection. The attack can 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 Marwal Infotech CMS 1.0, this vulnerability poses a significant risk to the confidentiality and integrity of their web application data. Exploitation could lead to unauthorized disclosure of sensitive information, including customer data, internal documents, or credentials stored in the database. Data tampering or deletion could disrupt business operations or damage organizational reputation. Given the remote and unauthenticated nature of the attack, any exposed CMS instance is at risk. This is particularly critical for organizations in regulated sectors such as finance, healthcare, or government, where data breaches can lead to regulatory penalties under GDPR and other compliance frameworks. Additionally, the absence of vendor patches means organizations must rely on internal mitigations, increasing operational overhead. The potential for attackers to leverage this vulnerability as an entry point for further network compromise or lateral movement also elevates the threat level. Overall, the vulnerability could undermine trust in affected organizations' digital services and lead to financial and reputational damage.

Summary

CVE-2025-5435 is a SQL Injection vulnerability identified in Marwal Infotech CMS version 1.0, specifically within the /page.php file. The vulnerability arises from improper sanitization or validation of the 'ID' parameter, which can be manipulated by an attacker to inject malicious SQL commands. This flaw allows an unauthenticated remote attacker to execute arbitrary SQL queries on the backend database without any user interaction or privileges. The vulnerability has been publicly disclosed, and although no known exploits are currently observed in the wild, the availability of exploit details increases the risk of exploitation. The vendor has not responded to notifications regarding this issue, and no patches or mitigations have been released. The CVSS v4.0 score is 6.9, indicating a medium severity level, reflecting the network attack vector, low complexity, no authentication required, and limited impact on confidentiality, integrity, and availability. The vulnerability could lead to unauthorized data access, data modification, or potentially database compromise depending on the backend database privileges and structure. Since the affected CMS is version 1.0, it is likely an early or legacy product, which may still be in use in some organizations. The lack of vendor response and patch availability increases the urgency for organizations to implement compensating controls or consider migration strategies.

References

Community reviews

Loading reviews…