CVE-2026-129169 in PMailinfo

Summary

by MITRE • 11/13/2026

PMail 2.5.0 through 2.9.8 contains a stored cross-site scripting vulnerability that allows authenticated users to inject scripts by sending unsanitized HTML through /api/email/send. Attackers can embed event-handler payloads like img onerror that execute when administrators view the message, enabling privileged API calls such as password changes for account takeover.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Analysis

by VulDB Data Team • 11/13/2026

The security flaw identified in PMail versions 2.5.0 through 2.9.8 represents a critical stored cross-site scripting vulnerability located within the email sending functionality of the application. This weakness is specifically triggered when authenticated users interact with the /api/email/send endpoint, which fails to properly sanitize or validate HTML content before storing it for later retrieval and display. Unlike reflected XSS attacks that require immediate user interaction with a crafted link, this stored variant persists on the server side, meaning the malicious payload remains active until manually removed from the database. This persistence significantly increases the attack surface, as any administrator or privileged user who views an email containing the injected script will inadvertently execute it within their own browser session context.

From a technical perspective, the vulnerability stems from insufficient input validation and output encoding mechanisms in the backend processing of incoming emails. The application accepts HTML-formatted messages without stripping out dangerous elements such as event handlers. Attackers can exploit this by embedding malicious JavaScript code using common vectors like img tags with onerror attributes or other DOM-based injection points. When an administrator opens a message containing these payloads, the browser interprets and executes the script as if it were part of the legitimate application interface. This execution occurs within the security context of the authenticated admin session, granting the attacker full access to all functionalities available to that user role without requiring additional authentication steps or token theft via traditional means.

The operational impact of this vulnerability is severe due to its potential for account takeover and privilege escalation. By leveraging the executed script in an administrator's browser, attackers can perform privileged API calls on behalf of the victim. Specific risks include changing password credentials, modifying user permissions, accessing sensitive email data, or altering application configuration settings. This capability effectively allows a lower-privileged authenticated user to compromise high-level administrative accounts, leading to a complete breach of confidentiality and integrity for the entire PMail deployment. The ability to automate these actions through scripts also means that attacks can be scaled rapidly across multiple targets without manual intervention per victim.

This vulnerability aligns with CWE-79, which classifies improper neutralization of input during web page generation as cross-site scripting. Furthermore, in terms of tactical mapping within the MITRE ATT&CK framework, this exploit falls under T1059 Command and Scripting Interpreter for code execution via browser-based scripts, and potentially T1078 Valid Accounts if used to escalate privileges or maintain persistence through compromised admin credentials. The attack vector is classified as Local Network with High Privileges required initially but resulting in higher privilege levels post-exploitation depending on the target user's role within PMail.

To mitigate this risk, immediate remediation should focus on implementing strict input validation and output encoding for all HTML content processed by the email system. Developers must ensure that only safe, whitelisted HTML tags are permitted while stripping or escaping dangerous elements such as script blocks, event handlers like onerror, and javascript: URIs. Utilizing a robust library for HTML sanitization is recommended over custom regex-based solutions to prevent bypasses. Additionally, implementing Content Security Policy headers can help mitigate the impact of any remaining XSS vectors by restricting where scripts are allowed to load from or execute within the application environment. Regular security audits and penetration testing focused on API endpoints should be conducted to identify similar flaws in other parts of the system before they can be exploited in production environments.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00276

KEV

no

Activities

very low

Sources

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!