Atomic Edge analysis of CVE-2026-28177: The Popup Maker WordPress plugin (versions <= 1.23.0) contains a stored cross-site scripting (XSS) vulnerability in its admin Extend page rendering logic. The component involved is the `PUM_Admin_Extend::render_extension_list()` function, which fails to properly sanitize and escape the extension catalog data before output. An unauthenticated attacker who can influence the extension catalog (e.g., via a compromised update source or by injecting into the JSON file through another vector) can store malicious scripts that execute in the browser of any admin user visiting the plugin's Extend page. The CVSS score is 7.2 (High).
Root Cause: The vulnerability stems from insufficient output escaping in `popup-maker/classes/Admin/Extend.php`, specifically in the `render_extension_list()` method. Prior to the patch, the function echoed the `slug`, `name`, `homepage`, `excerpt`, and `image` fields from the extension list JSON directly into HTML attributes and content. For example, the `slug` was echoed into the `class` attribute using `esc_attr( $extension['slug'] )` but the `name` was output with `esc_html()` only in some contexts, while the `homepage` URL used `esc_url()` but the `image` attribute was not always properly escaped. More critically, the `excerpt` field was passed to `wp_kses()` with a permissive allowed HTML set (`wp_kses_allowed_html( 'data' )`), but the patch reveals that the original code lacked explicit sanitization for the `image` URL and the `homepage` URL when constructing the link `href` without proper escaping in all branches. The patched version explicitly uses `esc_attr( $slug )`, `esc_url( $homepage )`, `esc_html( $name )`, and `esc_url( $image )`, and only allows `wp_kses()` with the same allowed set for the excerpt. Additionally, the patch introduces `rel="noreferrer noopener"` to the links, and removes the unsafe concatenation of UTM parameters. The root cause is the failure to sanitize and escape the extension data, which is presumably populated from a remote source (`includes/extension-list.json`) that could be attacker-controlled if the update mechanism is compromised, or if the JSON file is writable by an attacker.
Exploitation: An attacker can exploit this vulnerability by modifying the `includes/extension-list.json` file (or by intercepting and altering the plugin's update process) to include malicious JavaScript in the `name`, `homepage`, `excerpt`, or `image` fields. For instance, setting `homepage` to `javascript:alert(document.cookie)` or embedding an `onerror` event in the `image` URL. When an authenticated admin user accesses the Popup Maker Extend page (`/wp-admin/edit.php?post_type=popup&page=pum-extensions`), the injected script executes in the context of the admin's browser. Since the extension data is stored in a file and not sanitized at output, the XSS is persistent. An unauthenticated attacker could also potentially exploit this if they can chain another vulnerability to write to the JSON file, but the primary vector is through the plugin's update or data ingestion process. The vulnerability is unauthenticated on the attack side because the data source is not protected by authentication, but exploitation requires the ability to influence the JSON file (e.g., via a compromised server or man-in-the-middle attack on the plugin's update check).
Patch Analysis: The patch rewrites `render_extension_list()` to properly escape all output. It introduces `$slug = isset( $extension['slug'] ) ? sanitize_key( $extension['slug'] ) : '';` and similarly retrieves `$name`, `$homepage`, `$excerpt`, and `$image` with type casting. All output points now use `esc_attr( $slug )`, `esc_url( $homepage )`, `esc_html( $name )`, and `esc_url( $image )`. The `excerpt` is still passed through `wp_kses()` with the same allowed HTML, but this is considered safe because the allowed tags are restricted to data attributes only, not script or event handlers. The patch also adds `rel="noreferrer noopener"` to all links. This change fixes the vulnerability by ensuring that any malicious characters in the extension data are neutralized before being rendered, preventing script execution. The before behavior allowed raw JSON values to be echoed, while the after behavior sanitizes and escapes everything.
Impact: Successful exploitation of this vulnerability allows an attacker to execute arbitrary JavaScript in the context of an administrator's browser session. This can lead to full site takeover, including the creation of new admin accounts, installation of malicious plugins, theft of session cookies, and modification of site content. The vulnerability is stored, meaning the payload persists until the malicious data is removed. Since the Extend page is accessible to admins, the impact is high, though the attack complexity is moderate because it requires the ability to influence the extension catalog data.







