Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14057: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in tugbucket Multi-column Tag Map

0
Medium
VulnerabilityCVE-2025-14057cvecve-2025-14057cwe-79
Published: Wed Jan 07 2026 (01/07/2026, 09:21:06 UTC)
Source: CVE Database V5
Vendor/Project: tugbucket
Product: Multi-column Tag Map

Description

CVE-2025-14057 is a medium-severity stored Cross-Site Scripting (XSS) vulnerability in the Multi-column Tag Map WordPress plugin by tugbucket, affecting all versions up to 17. 0. 39. It allows authenticated users with administrator-level permissions on multi-site WordPress installations, where unfiltered_html is disabled, to inject malicious scripts via admin settings. These scripts execute when any user accesses the compromised page, potentially leading to data theft or session hijacking. Exploitation requires high privileges and no user interaction, with a CVSS score of 4. 4. No known exploits are currently in the wild, and no patches have been published yet. European organizations using multi-site WordPress setups with this plugin should prioritize mitigation to prevent potential abuse. Mitigations include restricting admin access, enabling strict input validation, and monitoring for suspicious admin activity.

AI-Powered Analysis

AILast updated: 01/14/2026, 15:57:27 UTC

Technical Analysis

CVE-2025-14057 identifies a stored Cross-Site Scripting (XSS) vulnerability in the Multi-column Tag Map plugin for WordPress, maintained by tugbucket. This vulnerability arises from improper neutralization of input during web page generation (CWE-79), specifically due to insufficient input sanitization and output escaping in the plugin's admin settings interface. The flaw affects all versions up to and including 17.0.39. It is exploitable only in multi-site WordPress installations where the 'unfiltered_html' capability is disabled, which restricts users from posting unfiltered HTML content. An attacker with administrator-level permissions or higher can inject arbitrary JavaScript payloads into the plugin's settings. These payloads are stored persistently and executed whenever any user visits the affected page, enabling potential session hijacking, credential theft, or other malicious actions. The vulnerability requires high privileges (administrator), no user interaction, and is remotely exploitable over the network. The CVSS v3.1 base score is 4.4 (medium severity), reflecting limited impact on confidentiality and integrity, no impact on availability, and a high attack complexity due to required privileges. No public exploits or patches are currently available, but the vulnerability is officially published and tracked. The scope is limited to multi-site WordPress environments using this plugin, which narrows the affected population but still poses a risk to organizations leveraging multi-site WordPress deployments for content management.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to those using WordPress multi-site installations with the Multi-column Tag Map plugin. Successful exploitation could lead to unauthorized script execution in the context of the affected site, potentially compromising user sessions, stealing sensitive data, or enabling further attacks such as privilege escalation or phishing. Although exploitation requires administrator-level access, insider threats or compromised admin accounts could leverage this vulnerability to persist malicious code. The impact on confidentiality and integrity is low to moderate, with no direct availability impact. Given the widespread use of WordPress in Europe, especially in sectors like media, education, and government that may use multi-site setups, the vulnerability could facilitate targeted attacks against these organizations. Additionally, the lack of patches increases the window of exposure. Organizations failing to restrict admin access or monitor plugin configurations are at higher risk. However, the requirement for high privileges and multi-site configuration limits the overall attack surface.

Mitigation Recommendations

European organizations should implement the following specific mitigations: 1) Restrict administrator-level access strictly to trusted personnel and enforce strong authentication mechanisms such as multi-factor authentication (MFA). 2) Audit WordPress installations to identify multi-site deployments using the Multi-column Tag Map plugin and assess whether 'unfiltered_html' is disabled. 3) Temporarily disable or remove the vulnerable plugin until a patch is released. 4) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious script injection attempts in admin settings. 5) Monitor WordPress admin logs for unusual configuration changes or script injections. 6) Educate administrators on the risks of stored XSS and safe plugin management practices. 7) Regularly update WordPress core and plugins to the latest versions once patches become available. 8) Consider isolating multi-site environments or limiting plugin usage to reduce attack surface. These targeted actions go beyond generic advice by focusing on access control, monitoring, and plugin management specific to this vulnerability's context.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-12-04T17:57:15.913Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695e4c117349d0379d7d56b0

Added to database: 1/7/2026, 12:05:37 PM

Last enriched: 1/14/2026, 3:57:27 PM

Last updated: 2/7/2026, 12:26:26 PM

Views: 40

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats