CVE-2025-49322
BaseFortify
Publication date: 2025-06-06
Last updated on: 2026-04-28
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-49322 is a Cross Site Scripting (XSS) vulnerability in the WordPress plugin '404 Page by SeedProd' versions prior to 1.0.2. It allows a malicious administrator to inject harmful scripts such as redirects or advertisements into the website. These scripts execute when visitors access the site, potentially compromising user experience or security. [1]
How can this vulnerability impact me? :
This vulnerability can allow an attacker with administrator privileges to inject malicious scripts that execute in visitors' browsers. This can lead to unwanted redirects, display of malicious advertisements, or other harmful HTML payloads, potentially compromising user trust and site integrity. However, the impact is considered low severity with a CVSS score of 5.9. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection involves checking if the vulnerable version of the '404 Page by SeedProd' WordPress plugin is installed (versions prior to 1.0.2). You can verify the plugin version via WordPress admin dashboard or by running commands on the server such as: 'wp plugin list' (using WP-CLI) to list installed plugins and their versions. Additionally, monitoring for unusual script injections or unexpected HTML payloads in 404 pages may indicate exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the '404 Page by SeedProd' plugin to version 1.0.2 or later, where the vulnerability is fixed. If updating is not immediately possible, applying Patchstack's virtual patching (vPatching) can provide automatic protection against this vulnerability until an official patch is applied. Limiting administrator privileges and monitoring for suspicious activity can also help reduce risk. [1]