CVE-2026-131726 in Coming Soon Page Plugininfo

Summary

by MITRE • 11/22/2026

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Awesomemotive Coming Soon Page, Under Construction & Maintenance Mode by SeedProd coming-soon allows DOM-Based XSS.This issue affects Coming Soon Page, Under Construction & Maintenance Mode by SeedProd: from n/a through 6.20.12.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Analysis

by VulDB Data Team • 11/22/2026

The vulnerability identified as a Cross-site Scripting (XSS) flaw within the Awesomemotive Coming Soon Page plugin for WordPress represents a significant security risk to web applications utilizing this specific maintenance mode solution. This particular instance is classified as DOM-Based XSS, which differs from stored or reflected variants in that the malicious script execution occurs on the client side through modifications of the Document Object Model rather than being directly returned by the server in an HTTP response. The vulnerability exists within versions ranging from n/a up to 6.20.12 of the Coming Soon Page, Under Construction & Maintenance Mode plugin developed by SeedProd. This broad version range indicates that the underlying code handling user input has lacked proper sanitization or validation mechanisms for a considerable period, leaving numerous deployments exposed to exploitation until an update addressing this specific flaw is applied.

From a technical perspective, DOM-Based XSS vulnerabilities arise when JavaScript processes data from an untrusted source and updates the DOM in a way that allows malicious scripts to execute. In the context of this plugin, it implies that user-controllable input, potentially derived from URL parameters, form fields, or other client-side sources, is being inserted into the HTML document without adequate neutralization of special characters such as angle brackets, quotes, and ampersands. When a victim interacts with a crafted payload, typically via a maliciously constructed link or through interaction with the plugin's interface if accessible to unauthenticated users, the browser interprets the injected script code as legitimate content. This allows an attacker to execute arbitrary JavaScript in the context of the vulnerable website, effectively bypassing same-origin policy restrictions and gaining control over the user's session within that domain.

The operational impact of this vulnerability is severe due to its potential for widespread exploitation against end-users visiting websites protected by this plugin. Attackers can leverage DOM-Based XSS to perform a variety of malicious actions including stealing sensitive cookies or authentication tokens, thereby hijacking administrative sessions and gaining full control over the WordPress installation. Additionally, attackers may redirect users to phishing sites designed to harvest credentials, deface the website's appearance, or deploy further malware such as cryptominers or ransomware onto visitor devices. Since maintenance mode pages are often public-facing entry points for websites undergoing development or repair, they attract significant traffic from diverse sources, increasing the likelihood of successful exploitation by automated bots scanning for vulnerable plugins. The trust users place in a website's domain is exploited to bypass browser security features that normally prevent cross-site attacks.

This vulnerability aligns with CWE-79, which defines Improper Neutralization of Input During Web Page Generation commonly known as Cross-site Scripting. Specifically, the DOM-based nature of this flaw corresponds closely to patterns found within the MITRE ATT&CK framework under techniques related to Client-Side Injection and potentially Command and Control if used for beaconing or data exfiltration. The lack of input validation allows an attacker to inject executable code directly into the client-side environment, exploiting weaknesses in how the JavaScript handles dynamic content updates. This is particularly dangerous because traditional server-side security controls like Web Application Firewalls may not always detect DOM-based attacks effectively since the malicious payload does not necessarily traverse the network stack in a recognizable format for all inspection points.

Mitigation strategies must prioritize immediate remediation through software updates and proactive defensive coding practices. The primary recommendation is to upgrade the Awesomemotive Coming Soon Page plugin to version 6.20.13 or later, where SeedProd has presumably implemented proper input sanitization and output encoding mechanisms to neutralize potentially dangerous characters before they are processed by JavaScript. For organizations unable to update immediately due to compatibility constraints, temporary mitigations include implementing strict Content Security Policy headers that restrict the execution of inline scripts and limit sources from which scripts can be loaded. Additionally, deploying a Web Application Firewall with rules capable of detecting common XSS payloads in URL parameters or form submissions can provide an additional layer of defense. Regular security audits and code reviews focusing on how user input is handled within client-side JavaScript are essential to prevent similar DOM-based vulnerabilities in future development cycles.

Responsible

Patchstack

Reservation

11/17/2026

Disclosure

11/22/2026

Moderation

accepted

CPE

ready

EPSS

0.00000

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!