CVE-2025-58808
BaseFortify
Publication date: 2025-09-05
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 | prettyphoto | 1.2.4 |
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 prettyPhoto Plugin versions up to 1.2.4. It allows attackers with contributor-level privileges to inject malicious scripts into web pages generated by the plugin. These scripts can execute when visitors access the compromised website, potentially causing redirects, displaying unwanted advertisements, or executing other harmful HTML payloads. [1]
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to attackers injecting malicious scripts that run in the browsers of visitors to the affected website. This can result in unwanted redirects, display of malicious advertisements, or other harmful actions that compromise user experience and security. However, exploitation requires contributor-level access, and the vulnerability is considered low severity and unlikely to be widely 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 malicious script injections in the prettyPhoto plugin, especially from users with contributor-level privileges. Since plugin-based malware scanners may be unreliable, it is recommended to perform server-side malware scanning and seek professional incident response if compromise is suspected. Specific commands are not provided in the resources. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) offered by Patchstack, which auto-mitigates the vulnerability without an official fix and without impacting performance. Additionally, restricting contributor-level privileges and monitoring for suspicious activity are advisable until an official patch is released. [1]