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-62896: Cross-Site Request Forgery (CSRF) in digitaldonkey Multilang Contact Form

0
High
VulnerabilityCVE-2025-62896cvecve-2025-62896
Published: Mon Oct 27 2025 (10/27/2025, 01:33:48 UTC)
Source: CVE Database V5
Vendor/Project: digitaldonkey
Product: Multilang Contact Form

Description

Cross-Site Request Forgery (CSRF) vulnerability in digitaldonkey Multilang Contact Form multilang-contact-form allows Stored XSS.This issue affects Multilang Contact Form: from n/a through <= 1.5.

AI-Powered Analysis

AILast updated: 01/20/2026, 22:47:05 UTC

Technical Analysis

CVE-2025-62896 identifies a Cross-Site Request Forgery (CSRF) vulnerability in the digitaldonkey Multilang Contact Form plugin, versions up to and including 1.5. This plugin is used to provide multilingual contact form functionality on websites, commonly integrated into WordPress environments. The vulnerability allows an attacker to craft malicious requests that, when executed by an unsuspecting authenticated user, cause the plugin to store malicious scripts (Stored XSS) within the application. The CSRF aspect means that the attacker can induce the victim’s browser to submit unauthorized requests without their consent, exploiting the trust a site has in the user's browser. The stored XSS payload can then be executed in the context of other users visiting the site, potentially leading to session hijacking, data theft, or further compromise of the web application. The CVSS 3.1 score of 8.8 reflects a network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The impact on confidentiality, integrity, and availability is high (C:H/I:H/A:H), indicating that successful exploitation can lead to severe consequences. No patches or known exploits are currently documented, but the vulnerability is publicly disclosed and should be treated as a critical risk. The plugin’s widespread use in multilingual websites increases the attack surface, especially in regions with significant WordPress adoption.

Potential Impact

For European organizations, this vulnerability can lead to unauthorized actions performed on their websites, resulting in stored malicious scripts that compromise user data and site integrity. Confidential information submitted through contact forms could be stolen or manipulated, damaging trust and potentially violating GDPR regulations. The integrity of the website content and user interactions can be undermined, leading to reputational damage and operational disruption. Availability could also be affected if attackers leverage the vulnerability to execute denial-of-service or defacement attacks. Organizations relying on the digitaldonkey Multilang Contact Form plugin, especially those in sectors handling sensitive customer data such as finance, healthcare, or government, face increased risk. The cross-site nature of the attack means that even users with minimal privileges can be targeted, broadening the scope of impact. Additionally, stored XSS can facilitate further attacks like phishing or malware distribution, amplifying the threat landscape for European entities.

Mitigation Recommendations

1. Immediately audit all websites using the digitaldonkey Multilang Contact Form plugin and identify versions at or below 1.5. 2. Apply vendor patches as soon as they become available; if no official patch exists, consider disabling or replacing the plugin with a secure alternative. 3. Implement anti-CSRF tokens in all form submissions to ensure requests originate from legitimate users. 4. Enforce strict input validation and output encoding to prevent stored XSS payloads from being injected or executed. 5. Employ Content Security Policy (CSP) headers to restrict the execution of unauthorized scripts. 6. Monitor web server logs and application behavior for unusual POST requests or suspicious activity indicative of CSRF or XSS exploitation attempts. 7. Educate users and administrators about the risks of clicking on unsolicited links that could trigger CSRF attacks. 8. Regularly update all web application components and plugins to minimize exposure to known vulnerabilities. 9. Conduct penetration testing focused on CSRF and XSS vectors to validate the effectiveness of mitigations. 10. Consider web application firewalls (WAFs) configured to detect and block CSRF and XSS attack patterns.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
Patchstack
Date Reserved
2025-10-24T14:24:16.561Z
Cvss Version
null
State
PUBLISHED

Threat ID: 68fed02e23a7bbed324acb52

Added to database: 10/27/2025, 1:51:42 AM

Last enriched: 1/20/2026, 10:47:05 PM

Last updated: 2/4/2026, 1:03:21 PM

Views: 46

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