CVE-2025-58212
BaseFortify
Publication date: 2025-08-27
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 |
|---|---|---|
| epeken | epeken_all_kurir | * |
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 Cross Site Scripting (XSS) issue in the WordPress Epeken All Kurir Plugin (versions up to 2.0.1). It allows attackers to inject malicious scripts, such as redirects, advertisements, or other HTML payloads, which execute when visitors access the affected website. The vulnerability is DOM-Based XSS, meaning the malicious script is executed as part of the web page generation in the browser. [1]
How can this vulnerability impact me? :
The vulnerability can lead to attackers executing malicious scripts on your website visitors' browsers. This can result in unwanted redirects, display of unauthorized advertisements, or other harmful actions that compromise user experience and security. Exploitation requires only contributor-level privileges and can lead to partial compromise of confidentiality, integrity, and availability of the affected system, as indicated by the CVSS score. Automated and opportunistic attacks are typical, so any vulnerable site may be targeted. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves checking the version of the Epeken All Kurir WordPress plugin installed on your system. Since the vulnerability affects versions up to 2.0.1, verifying the plugin version is key. Additionally, monitoring for suspicious script injections or unexpected HTML payloads in web traffic could indicate exploitation attempts. Specific commands are not provided in the resources, but you can check the plugin version via WordPress CLI with: `wp plugin list` or by inspecting the plugin files. For deeper inspection, server-side malware scanning is recommended as plugin-based scanners may be unreliable. [1]
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Epeken All Kurir plugin to version 2.0.2 or later, where the vulnerability is fixed. If updating immediately is not possible, enabling Patchstack's virtual patching (vPatching) can provide immediate protection without impacting performance. Additionally, enabling auto-updates for vulnerable plugins is recommended to ensure timely protection. In case of suspected compromise, professional incident response or server-side malware scanning should be conducted. [1]