VulnerabilityPublished 26 Dec 2025Updated 24 Feb 2026

CVE-2025-15093: sunkaifei FlyCMS · Cross-site Scripting

Affects sunkaifei FlyCMSSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 15:59 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 34% 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:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, 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

AI-suggested

Implement strict input validation and output encoding on the redirectUrl parameter to neutralize malicious scripts.
Employ a web application firewall (WAF) with rules to detect and block XSS attack patterns targeting the redirectUrl parameter.
Restrict administrative interface access by IP whitelisting or VPN to reduce exposure to untrusted networks.
Use Content Security Policy (CSP) headers to limit the execution of unauthorized scripts in browsers.
Educate administrators and users to avoid clicking suspicious or unsolicited links that may contain malicious payloads.
Monitor web server and application logs for unusual requests containing suspicious redirectUrl parameters.
If possible, temporarily disable or restrict the vulnerable functionality until an official patch or update is released.
Consider deploying runtime application self-protection (RASP) solutions to detect and block exploitation attempts in real time.
Engage with the FlyCMS community or maintainers to encourage timely patch development and disclosure.
Regularly review and update all third-party components and dependencies to minimize exposure to known vulnerabilities.

Description

A security flaw has been discovered in sunkaifei FlyCMS up to abbaa5a8daefb146ad4d61027035026b052cb414. The affected element is an unknown function of the file src/main/java/com/flycms/web/system/IndexAdminController.java of the component Admin Login. Performing a manipulation of the argument redirectUrl results in cross site scripting. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The primary impact of CVE-2025-15093 is the compromise of confidentiality and integrity for users of FlyCMS administrative interfaces. Successful exploitation allows attackers to execute arbitrary JavaScript in the context of the victim’s browser, potentially leading to session hijacking, theft of authentication tokens, or unauthorized actions performed on behalf of the user. This can result in unauthorized access to sensitive administrative functions or data within the CMS. Although availability is not directly affected, the indirect consequences of compromised administrative accounts could lead to further system manipulation or data loss. Organizations relying on FlyCMS for website or content management may face reputational damage, data breaches, or unauthorized content modifications. The lack of vendor response and absence of patches increases the risk exposure, especially since the exploit code is publicly available. The medium CVSS score reflects that while the attack requires user interaction, it can be performed remotely without authentication, broadening the potential attack surface. Given FlyCMS’s niche market, the impact is more pronounced for organizations using this specific CMS, particularly those with public-facing administrative portals.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:29 UTC

Technical details

References

Community reviews

Related threats