CVE-2025-12264VulnerabilityPublished 27 Oct 2025

CVE-2025-12264: Wisencode · Cross Site Scripting

Affects WisencodeSource CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

5.1Medium

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

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

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
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

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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 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-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

Affected software

Product	Affected	Fixed in
Wisencode	Affected =20251012	Fixed in–

AI-suggested

European organizations using Wisencode should implement the following specific mitigations: 1) Employ web application firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the /support-ticket/create endpoint, focusing on suspicious script tags or event handlers in the 'Message' parameter. 2) Conduct input validation and output encoding on the server side as a compensating control if source code access or customization is possible, sanitizing user inputs to neutralize script injections. 3) Educate support staff and users about the risks of interacting with suspicious support tickets and encourage vigilance against unexpected or unusual messages. 4) Monitor logs and network traffic for anomalous requests or patterns indicative of exploitation attempts. 5) Isolate the support ticket system from critical internal networks to limit lateral movement if compromise occurs. 6) Engage with Wisencode vendor or community forums to track any forthcoming patches or updates. 7) Consider deploying Content Security Policy (CSP) headers to restrict script execution origins and reduce the impact of XSS attacks. These targeted actions go beyond generic advice by focusing on the specific vulnerable component and attack vector.

Description

A security flaw has been discovered in Wisencode up to 20251012. Affected by this vulnerability is an unknown functionality of the file /support-ticket/create of the component Create Support Ticket Handler. The manipulation of the argument Message results in cross site scripting. The attack may be launched remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, this vulnerability poses a risk primarily to the confidentiality and integrity of user sessions and data accessed through the Wisencode support ticket system. Attackers exploiting this XSS flaw could hijack user sessions, steal authentication tokens, or conduct phishing attacks by injecting malicious scripts that manipulate the user interface or capture input data. This can lead to unauthorized access to sensitive support ticket information or broader system compromise if the support portal integrates with other internal systems. The impact is heightened in sectors where customer support platforms handle sensitive personal or business data, such as finance, healthcare, and government services. Additionally, reputational damage and regulatory consequences under GDPR could arise if personal data is compromised. Since exploitation requires user interaction, social engineering campaigns targeting support staff or customers could be used to trigger the attack. The absence of vendor patches increases the window of exposure, necessitating immediate risk mitigation by affected organizations.

Summary

CVE-2025-12264 is a cross-site scripting vulnerability identified in Wisencode software versions up to 20251012. The flaw exists in the Create Support Ticket Handler component, specifically within the /support-ticket/create endpoint, where the 'Message' parameter is improperly sanitized. This allows an attacker to inject malicious JavaScript code that executes in the context of users who view the crafted support ticket messages. The vulnerability is remotely exploitable without requiring authentication, though user interaction is necessary to trigger the malicious script, such as viewing or interacting with the support ticket containing the injected payload. The vendor was notified early but has not issued any response or patch, leaving the vulnerability unmitigated. The CVSS 4.0 base score is 5.1 (medium severity), reflecting the network attack vector, low attack complexity, no privileges required, but requiring user interaction and resulting in limited integrity impact and no confidentiality or availability impact. While no known exploits are currently reported in the wild, the lack of vendor response increases the risk of future exploitation. This vulnerability can lead to session hijacking, theft of sensitive information, or social engineering attacks targeting users of the Wisencode support ticket system. Organizations relying on Wisencode should assess their exposure and implement compensating controls until a patch is available.

References

Community reviews

Loading reviews…