CVE-2025-58005
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 |
|---|---|---|
| smartdatsoft | dricub | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-58005 is a Server-Side Request Forgery (SSRF) vulnerability in the WordPress DriCub Theme up to version 2.9. It allows an unauthenticated attacker to make the affected website send arbitrary HTTP requests to attacker-controlled domains. This can lead to exposure of sensitive information from other services running on the same system. The vulnerability is classified as low severity with a CVSS score of 5.4 and falls under the OWASP Top 10 category A3: Injection. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to make the affected website perform arbitrary HTTP requests, potentially exposing sensitive information from other services on the same system. Although the risk is considered limited due to low severity and low likelihood of exploitation, it can still lead to information disclosure and unauthorized access to internal resources. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
There is no specific detection command or method provided for this vulnerability. However, monitoring for unusual outbound HTTP requests from the affected WordPress DriCub Theme (up to version 2.9) could help identify exploitation attempts. Since the vulnerability allows arbitrary HTTP requests to attacker-controlled domains, network monitoring tools or web application firewalls (WAF) configured to log or block suspicious outbound requests may assist in detection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include applying virtual patching (vPatching) as recommended by Patchstack, which auto-mitigates the vulnerability even without an official patch. Users should monitor for updates from the vendor or security advisories and consider implementing network-level controls such as restricting outbound HTTP requests from the affected system to untrusted domains. Since no official fix is available as of the report date, virtual patching and monitoring are the primary recommended actions. [1]