VulnerabilityPublished 31 Jan 2024Updated 29 May 2025

CVE-2024-24571: WillyXJ facileManager · Basic XSS

Affects WillyXJ facileManagerSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: 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 impacted component.
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 on 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 31 Jan 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 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
GitHubwillyxj/facileManager`pkg:github/willyxj/facileManager`Other threats	Affected <=4.5.0	Fixed in–

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

AI-suggested

Organizations should immediately assess their usage of facileManager and identify if any instances are running version 4.5.0 or earlier. Until an official patch is released, mitigation can include implementing strict input validation and output encoding on all user-supplied data within the application, ideally through web application firewalls (WAFs) configured to detect and block XSS payloads targeting facileManager endpoints. Restricting access to the application to trusted networks and enforcing strong authentication and session management controls can reduce exploitation risk. Additionally, monitoring logs for unusual input patterns or script injection attempts can provide early detection. Organizations should also prepare to update to a patched version once available and consider conducting security assessments or penetration testing focused on XSS vulnerabilities in their web applications.

Description

facileManager is a modular suite of web apps built with the sysadmin in mind. For the facileManager web application versions 4.5.0 and earlier, we have found that XSS was present in almost all of the input fields as there is insufficient input validation.

Impact

For European organizations, the presence of this XSS vulnerability in facileManager could lead to unauthorized access to administrative sessions, data leakage, or manipulation of system configurations if exploited. Since facileManager targets sysadmins, exploitation could compromise critical infrastructure management tools, potentially affecting the integrity and confidentiality of system management operations. This could disrupt IT operations, lead to unauthorized changes, or facilitate further attacks within the network. The medium severity suggests that while the vulnerability is exploitable remotely and with low complexity, the prerequisite of some level of privileges limits the attack surface somewhat. However, organizations relying on facileManager for system administration should consider the risk significant, especially in sectors with strict data protection regulations like GDPR, where data breaches can result in heavy fines and reputational damage.

Summary

CVE-2024-24571 is a medium-severity vulnerability classified under CWE-80, indicating improper neutralization of script-related HTML tags, commonly known as a Cross-Site Scripting (XSS) vulnerability. This vulnerability affects the facileManager web application developed by WillyXJ, specifically versions 4.5.0 and earlier. facileManager is a modular suite of web applications designed for system administrators. The vulnerability arises due to insufficient input validation on nearly all input fields within the application, allowing attackers to inject malicious scripts. These scripts can execute in the context of the victim's browser when they view the affected pages, potentially leading to session hijacking, defacement, or redirection to malicious sites. The CVSS v3.1 score of 5.4 reflects a medium impact with network attack vector, low attack complexity, requiring privileges but no user interaction, and limited confidentiality and integrity impact without affecting availability. No known exploits are currently reported in the wild, and no patches have been linked yet.

CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) (opens in a new tab)
Variant weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages.
Implementation
Carefully check each input parameter against a rigorous positive specification (allowlist) defining the specific characters and format allowed. All input should be neutralized, not just parameters that the user is supposed to specify, but all data in the request, including hidden fields, cookies, headers, the URL…
Implementation · Output Encoding
Use and specify an output encoding that can be handled by the downstream component that is reading the output. Common encodings include ISO-8859-1, UTF-7, and UTF-8.
Implementation
With Struts, write all data from form beans with the bean's filter attribute set to true.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
V5.3.3 (opens in a new tab)
Attack patterns
XSS Targeting Non-Script Elements (opens in a new tab)
PHP Remote File Inclusion (opens in a new tab)
XSS Through HTTP Query Strings (opens in a new tab)
XSS Through HTTP Headers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jul 2025, 01:57 UTC

WeaknessesCWE-80

Technical details

References

Community reviews

Related threats