Skip to main content
CVE-2024-31741VulnerabilityPublished Updated

CVE-2024-31741: MiniCMS · n/a

Affects MiniCMSSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Apr 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
GitHubbg5sbk/MiniCMSpkg:github/bg5sbk/MiniCMSOther threatsAffected
  • =1.11
Fixed in–

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

AI-suggested

To mitigate CVE-2024-31741, organizations should implement the following specific measures: 1) Apply strict input validation and sanitization on all URL parameters and user inputs to prevent injection of malicious scripts. 2) Employ robust output encoding/escaping techniques when rendering user-supplied data in web pages to neutralize potential XSS payloads. 3) Implement Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts and reduce the impact of XSS attacks. 4) Educate users about the risks of clicking on suspicious links, especially within authenticated sessions, to reduce successful exploitation via social engineering. 5) Monitor web application logs for unusual URL access patterns or suspicious parameters indicative of attempted exploitation. 6) Use web application firewalls (WAFs) with updated rules to detect and block XSS attack vectors targeting MiniCMS. 7) Stay alert for official patches or updates from MiniCMS developers and apply them promptly once available. 8) Consider isolating MiniCMS instances or restricting access to trusted networks to limit exposure. These targeted actions go beyond generic advice and address the specific nature of this vulnerability.

Description

Cross Site Scripting vulnerability in MiniCMS v.1.11 allows a remote attacker to run arbitrary code via crafted string in the URL after login.

References

Community reviews

Loading reviews…