VulnerabilityPublished 28 Jan 2026

CVE-2025-13983: Drupal Tagify · Cross-site Scripting

Affects Drupal TagifySource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 1.2.44 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.4Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.2.44

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Changed
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 28 Jan 2026
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

Upgrade Drupal Tagify to 1.2.44.

Affected software

Product	Affected	Fixed in
DrupalTagify	Affected <1.2.44	Fixed in 1.2.44

AI-suggested

Immediately upgrade the Drupal Tagify module to version 1.2.44 or later once available to address the vulnerability.
Implement strict input validation and sanitization on all user-supplied data, especially in fields enhanced by Tagify, to prevent injection of malicious scripts.
Deploy Content Security Policies (CSP) to restrict the execution of unauthorized scripts and reduce the impact of potential XSS attacks.
Educate users and administrators about the risks of phishing and social engineering attacks that could trigger this vulnerability, emphasizing cautious interaction with unexpected links or inputs.
Monitor web server and application logs for unusual activity or error messages that may indicate attempted exploitation.
Use web application firewalls (WAFs) with updated rule sets to detect and block common XSS payloads targeting Drupal applications.
Conduct regular security assessments and penetration testing focusing on input handling and client-side script execution.
Ensure that session management mechanisms are robust, including the use of HttpOnly and Secure flags on cookies to mitigate session hijacking risks.

Description

CVE-2025-13983 is a medium severity Cross-Site Scripting (XSS) vulnerability in the Drupal Tagify module versions before 1.2.44. It arises from improper neutralization of input during web page generation, allowing attackers with low privileges and requiring user interaction to inject malicious scripts. The vulnerability impacts confidentiality and integrity by enabling script execution in the context of authenticated users, potentially leading to session hijacking or data manipulation. No known exploits are currently reported in the wild. European organizations using Drupal with the vulnerable Tagify versions should prioritize patching to mitigate risks. The vulnerability has a CVSS score of 5.4, reflecting its moderate impact and exploitability. Countries with significant Drupal adoption and critical web infrastructure, such as Germany, France, and the UK, are most likely to be affected.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to web applications built on Drupal that utilize the Tagify module. Successful exploitation could lead to unauthorized script execution in users’ browsers, compromising session tokens, user credentials, or enabling actions on behalf of authenticated users. This can result in data breaches, defacement, or further lateral attacks within the organization’s network. Given Drupal's popularity among government, educational, and commercial websites in Europe, the impact could extend to sensitive public sector data and critical infrastructure portals. The vulnerability’s requirement for user interaction somewhat limits automated widespread exploitation but does not eliminate targeted phishing or social engineering attacks. The scope change in the CVSS vector suggests that the vulnerability could affect multiple components or users beyond the initial injection point, increasing potential damage. Organizations handling personal data under GDPR must consider the regulatory implications of such breaches, including notification requirements and potential fines. The absence of known exploits provides a window for proactive mitigation, but the medium severity rating underscores the need for timely patching and monitoring.

CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
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)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

drupal.org/sa-contrib-2025-121 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Feb 2026, 08:52 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats