CVE-2025-58648
BaseFortify
Publication date: 2025-09-22
Last updated on: 2026-04-23
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| patchstack | simple_jwt_login | * |
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?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the WordPress Simple JWT Login Plugin (versions up to 3.6.4). It allows attackers with contributor-level privileges to inject malicious scripts, such as redirects or advertisements, into web pages generated by the plugin. These scripts execute when visitors access the affected site, potentially compromising user interactions. [1]
How can this vulnerability impact me? :
The vulnerability can lead to attackers injecting malicious scripts that execute in the browsers of site visitors. This can result in unwanted redirects, display of unauthorized advertisements, or other harmful HTML payloads. Although the severity is considered low and exploitation likelihood is limited, it can still harm user trust, site integrity, and potentially lead to further attacks if exploited. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for injected malicious scripts in web pages generated by the Simple JWT Login plugin up to version 3.6.4. Since plugin-based malware scanners may be unreliable, manual inspection of web page source code for unexpected scripts or payloads is recommended. Network monitoring tools can be used to detect unusual script injections or redirects originating from affected pages. Specific commands are not provided in the available resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) provided by Patchstack, which offers automatic protection despite the absence of an official patch. Additionally, restricting contributor-level privileges to trusted users can reduce exploitation risk. If a site is suspected to be compromised, professional incident response services should be engaged. Users should also monitor and audit their sites for suspicious activity related to this vulnerability. [1]