CVE-2024-31551VulnerabilityPublished 26 Apr 2024Updated 2 Aug 2024

CVE-2024-31551: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

7.5High

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

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Apr 2024
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. Immediately restrict access to the vulnerable script lib/admin/image.admin.php by limiting it to trusted IP addresses or internal networks using firewall rules or web server access controls. 2. Deploy a web application firewall (WAF) with rules to detect and block directory traversal patterns in GET requests targeting the vulnerable endpoint. 3. Monitor file system integrity using tools like Tripwire or OSSEC to detect unauthorized file deletions promptly. 4. Regularly back up critical files and configurations to enable rapid recovery in case of file deletion. 5. If possible, upgrade cmseasy to a version where this vulnerability is patched once available. 6. Conduct thorough code review and input validation improvements on the affected script to sanitize and validate all user inputs rigorously. 7. Implement logging and alerting for suspicious access patterns to the admin directory to detect exploitation attempts early. 8. Educate system administrators about this vulnerability and ensure they follow the principle of least privilege for web server and application permissions to limit damage scope.

Description

Directory Traversal vulnerability in lib/admin/image.admin.php in cmseasy v7.7.7.9 20240105 allows attackers to delete arbitrary files via crafted GET request.

Impact

The primary impact of CVE-2024-31551 is on the integrity of affected systems, as attackers can delete arbitrary files remotely without authentication. This can lead to significant operational disruptions, including website downtime, loss of critical configuration files, or deletion of application data. Such disruptions may cause financial losses, damage to reputation, and increased recovery costs. While confidentiality and availability are not directly impacted, the deletion of files could indirectly cause denial of service if essential files are removed. The ease of exploitation and lack of required privileges increase the threat level, making it attractive for opportunistic attackers and potentially for targeted attacks against organizations relying on cmseasy. Organizations with web-facing cmseasy installations are at risk of compromise, especially if they have not implemented access controls or monitoring. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the potential for future attacks as exploit code may be developed.

CWE-26Path Traversal: '/dir/../filename' (opens in a new tab)
Variant weakness
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/dir/../filename" sequences that can resolve to a location that is outside of that directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

yuque.com/sickle-ffnce/awixr8/qu8i0p9y0h277m6u (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 12:42 UTC

WeaknessesCWE-26

Technical details

References

Community reviews

Related threats