CVE-2026-119157 in Capabilities User Role Access Control, Admin Area Permissions Plugininfo

Summary

by MITRE • 11/21/2026

The PublishPress Capabilities: User Role Access Control, Admin Area Permissions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'page_elements' parameter in all versions up to, and including, 2.53.0 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Successful exploitation requires an administrator to open a Profile Features capture window and save at least one of the attacker-supplied rows on the Profile Features screen, which represents the ordinary documented use of the feature and leaves no visible indication to the administrator that malicious data was submitted.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Analysis

by VulDB Data Team • 11/21/2026

The vulnerability identified in PublishPress Capabilities versions up to 2.53.0 constitutes a significant security risk within WordPress environments due to its potential for persistent code injection. This flaw is classified as a Stored Cross-Site Scripting, or XSS, vulnerability that stems directly from insufficient input sanitization and the absence of proper output escaping when handling the page_elements parameter. Unlike reflected XSS attacks where malicious scripts are executed immediately via a crafted link, stored vulnerabilities persist within the application's database. In this specific case, the attacker injects arbitrary web scripts into user profile data fields managed by the plugin. Because the input is not adequately filtered before storage and subsequently rendered without escaping in administrative interfaces, any browser that loads the compromised page will execute the injected JavaScript code as if it were part of the legitimate application logic.

The operational impact of this vulnerability is severe because it allows for persistent compromise of user sessions and potentially sensitive site data. The attack vector requires an authenticated attacker with subscriber-level access or higher to interact with the Profile Features screen. Specifically, the attacker must inject malicious payloads into rows that are then saved by a privileged administrator through the normal operation of opening the capture window and saving settings. This social engineering aspect is particularly dangerous because it leverages trusted administrative actions to propagate malware. Once executed, the script can perform various malicious activities such as stealing session cookies, hijacking admin sessions, defacing the website, or redirecting users to phishing sites. The lack of visible indicators means that administrators may remain unaware of the compromise until significant damage has occurred, making detection and remediation more difficult without proactive monitoring.

From a technical classification perspective, this vulnerability aligns with CWE-79, which covers Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. The specific mechanism involves failing to sanitize user-supplied input before storing it in the database and failing to escape output when rendering that data in an HTML context. This dual failure allows raw script tags or event handlers to persist across page loads. Furthermore, this attack scenario maps closely to MITRE ATT&CK technique T1059.007, which refers to JavaScript under Execution on Web Bases. The attacker utilizes the application's own functionality against itself, turning a legitimate feature into an entry point for malicious code execution. This highlights the importance of defense-in-depth strategies where input validation is applied at multiple layers rather than relying solely on client-side checks or single-point sanitization functions that may be bypassed by sophisticated payloads.

Mitigation and remediation efforts must focus primarily on updating to a patched version of the PublishPress Capabilities plugin if one has been released, as this addresses the root cause within the codebase. For organizations unable to patch immediately, implementing strict Content Security Policy headers can help mitigate the impact by restricting the sources from which scripts are allowed to execute, thereby preventing many common XSS payloads from running even if they are injected into the DOM. Additionally, administrators should be educated on verifying the integrity of data entered through plugin interfaces, although this is a secondary control since the flaw relies on trusted users inadvertently saving malicious content. Regular security audits and code reviews focusing on input sanitization libraries such as wp_kses in WordPress development practices can prevent similar vulnerabilities from being introduced into other plugins or themes. Ensuring that all dynamic content rendered to the browser is properly escaped using functions like esc_html or esc_attr is critical for maintaining web application integrity against stored XSS attacks.

Responsible

Wordfence

Reservation

10/29/2026

Disclosure

11/21/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!