CVE-2026-59077 in Editoinfo

Summary

by MITRE • 11/13/2026

Edito CMS is vulnerable to Stored XSS via content parameter in Tiny editor functionality. Authenticated attacker can inject arbitrary HTML and JS into website, which will be rendered/executed when user tries to edit changed entry.

This issue was fixed in version 5.10.2607.  Hotfixes for older versions (5.8) have also been released.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/13/2026

The vulnerability identified within Edito CMS represents a critical security flaw located specifically within the TinyMCE editor functionality, classified as a Stored Cross-Site Scripting injection via the content parameter. This type of vulnerability allows an attacker to inject malicious client-side scripts into web pages viewed by other users or administrators. Unlike reflected XSS where the payload is delivered through a URL query string and executed immediately upon request, stored XSS persists on the target server's database or file system. In this specific instance, the flaw resides in how the CMS processes and subsequently renders content entered through its rich text editor interface. When an authenticated user submits data containing malicious HTML or JavaScript code, the application fails to adequately sanitize or encode these inputs before storing them for later retrieval.

The operational impact of this vulnerability is significant because it requires authentication to exploit, which limits the attack surface but increases the severity once access is gained. An attacker with valid credentials can craft a post or edit an existing entry by embedding malicious script tags within the content field. These scripts remain dormant in the database until another user, potentially an administrator or any other authenticated individual, attempts to view or re-edit that specific entry. Upon rendering the page, the browser executes the injected JavaScript in the context of the victim's session. This can lead to severe consequences such as session hijacking, where the attacker steals authentication cookies and takes over the victim's account; credential theft through fake login forms embedded within the content; defacement of the website by altering its visual presentation; or redirection of users to malicious phishing sites designed to harvest sensitive information further compromising organizational security.

From a classification perspective, this vulnerability aligns with CWE-79 Improper Neutralization of Input During Web Page Generation known commonly as Cross-site Scripting and more specifically falls under Stored XSS patterns often associated with CWE-83 if the input is processed by an API or backend service before storage. The exploitation technique maps directly to MITRE ATT&CK techniques such as T1059 Command and Scripting Interpreter for executing arbitrary code within the victim's browser environment, and potentially T1204 User Execution if social engineering tactics are used to trick users into clicking on manipulated links that trigger the stored payload. The persistence of the attack vector means that remediation is not just about fixing a single input field but requires a comprehensive review of how all user-generated content is handled throughout the application lifecycle, ensuring that output encoding and input validation are consistently applied across all entry points including API endpoints used by the TinyMCE integration.

Mitigation strategies must prioritize immediate patching to version 5.10.2607 or applying the available hotfixes for older versions like 5.8 which address this specific flaw in the content parameter handling. Beyond updating software, administrators should implement strict Content Security Policy headers that restrict script execution sources and prevent inline scripts from running unless explicitly whitelisted, thereby mitigating the impact even if an injection occurs. Additionally, implementing robust input validation on both client-side and server-side is essential to reject or properly encode special characters before they reach the storage layer. Regular security audits focusing on rich text editors are recommended as these components often introduce complex parsing logic that can inadvertently bypass basic sanitization rules. Monitoring logs for unusual patterns of content submission involving script tags can also aid in early detection of attempted exploitation activities by malicious insiders or compromised accounts.

Responsible

CERT-PL

Reservation

07/02/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00239

KEV

no

Activities

very low

Sources

Want to stay up to date on a daily basis?

Enable the mail alert feature now!