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-13958: CWE-79 Cross-Site Scripting (XSS) in YaMaps for WordPress Plugin

0
Medium
VulnerabilityCVE-2025-13958cvecve-2025-13958cwe-79
Published: Mon Dec 29 2025 (12/29/2025, 06:00:10 UTC)
Source: CVE Database V5
Product: YaMaps for WordPress Plugin

Description

The YaMaps for WordPress Plugin WordPress plugin before 0.6.40 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.

AI-Powered Analysis

AILast updated: 12/30/2025, 23:12:36 UTC

Technical Analysis

CVE-2025-13958 is a Stored Cross-Site Scripting (XSS) vulnerability identified in the YaMaps for WordPress plugin, specifically in versions prior to 0.6.40. The root cause is the plugin's failure to properly validate and escape certain shortcode attributes before outputting them on pages or posts where the shortcode is embedded. Shortcodes in WordPress allow users to embed dynamic content, and improper handling of their attributes can lead to injection of malicious scripts. This vulnerability enables users with contributor role or higher—who have permissions to add or edit posts—to inject persistent malicious JavaScript code. When other users or administrators view the affected page or post, the malicious script executes in their browsers, potentially leading to session hijacking, defacement, or redirection to malicious sites. The CVSS v3.1 score is 5.9 (medium severity), reflecting that the attack vector is network-based, requires low attack complexity, but needs privileges (PR:H) and user interaction (UI:R). The scope is changed (S:C), indicating that the vulnerability affects resources beyond the initially vulnerable component. Although no known exploits are reported in the wild, the vulnerability poses a risk especially on multi-user WordPress sites where contributors can add content. The vulnerability impacts confidentiality, integrity, and availability to a limited degree, as the injected scripts can steal cookies or perform actions on behalf of users. The plugin is widely used for embedding maps, and failure to patch this vulnerability could lead to reputational damage and compromise of user data.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to websites running WordPress with the YaMaps plugin installed. Organizations that allow contributors or multiple content editors to publish posts are particularly vulnerable. Exploitation could lead to theft of session cookies, unauthorized actions performed in the context of logged-in users, and potential defacement or redirection attacks. This can result in loss of user trust, data leakage, and potential compliance issues under GDPR if personal data is compromised. The impact is more pronounced for organizations relying on WordPress for public-facing websites, intranets, or portals with multiple content contributors. Additionally, sectors such as media, education, and government agencies in Europe that use WordPress extensively could face reputational damage and operational disruption if exploited. Although the vulnerability requires authenticated access, insider threats or compromised contributor accounts could be leveraged by attackers. The absence of known exploits in the wild currently reduces immediate risk but does not eliminate the threat, especially as exploit code could be developed given the public disclosure.

Mitigation Recommendations

European organizations should immediately update the YaMaps for WordPress plugin to version 0.6.40 or later where the vulnerability is patched. If updating is not immediately possible, restrict contributor and higher roles from using the vulnerable shortcode or disable the plugin temporarily. Implement strict input validation and output escaping on shortcode attributes at the application level if custom code is used. Employ Web Application Firewalls (WAFs) with rules to detect and block typical XSS payloads targeting shortcode parameters. Regularly audit user roles and permissions to ensure only trusted users have contributor or higher access. Monitor website content for suspicious scripts or unexpected changes. Educate content contributors about the risks of injecting untrusted content. Finally, maintain regular backups and incident response plans to quickly recover from potential exploitation.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
WPScan
Date Reserved
2025-12-03T14:38:29.195Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695450b2db813ff03e2bee60

Added to database: 12/30/2025, 10:22:42 PM

Last enriched: 12/30/2025, 11:12:36 PM

Last updated: 2/7/2026, 10:25:31 AM

Views: 29

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