CVE-2026-39695 | Podigee Plugin up to 1.4.0 on WordPress server-side request forgery

VDB-356207 · CVE-2026-39695 · GCVE-0-2026-39695 PODIGEE PLUGIN UP TO 1.4.0 ON WORDPRESS SERVER-SIDE REQUEST FORGERY HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 6.3 $0-$5k 0.99+ Summaryinfo A vulnerability was found in Podigee Plugin up to 1.4.0 on WordPress. It has been classified as critical. Impacted is an unknown function. The manipulation leads to server-side request forgery. This vulnerability is uniquely identified as CVE-2026-39695. The attack is possible to be carried out remotely. No exploit exists. Detailsinfo A vulnerability was found in Podigee Plugin up to 1.4.0 on WordPress and classified as critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a server-side request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is: Server-Side Request Forgery (SSRF) vulnerability in podigee Podigee podigee allows Server Side Request Forgery.This issue affects Podigee: from n/a through <= 1.4.0. The weakness was disclosed by Nabil Irawan. It is possible to read the advisory at patchstack.com. The identification of this vulnerability is CVE-2026-39695 since 04/07/2026. The exploitation is known to be easy. The attack may be initiated remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/08/2026). There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. Productinfo Type WordPress Plugin Name Podigee Plugin Version 1.0 1.1 1.2 1.3 1.4.0 CPE 2.3info 🔒 🔒 🔒 CPE 2.2info 🔒 🔒 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv3info VulDB Meta Base Score: 6.3 VulDB Meta Temp Score: 6.3 VulDB Base Score: 6.3 VulDB Temp Score: 6.3 VulDB Vector: 🔒 VulDB Reliability: 🔍 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Server-side request forgery CWE: CWE-918 CAPEC: 🔒 ATT&CK: 🔒 Physical: No Local: No Remote: Yes Availability: 🔒 Status: Not defined Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/07/2026 CVE reserved 04/08/2026 +1 days Advisory disclosed 04/08/2026 +0 days VulDB entry created 04/08/2026 +0 days VulDB entry last update Sourcesinfo Advisory: patchstack.com Researcher: Nabil Irawan Status: Confirmed CVE: CVE-2026-39695 (🔒) GCVE (CVE): GCVE-0-2026-39695 GCVE (VulDB): GCVE-100-356207 Entryinfo Created: 04/08/2026 12:58 Changes: 04/08/2026 12:58 (54) Complete: 🔍 Cache ID: 99:49A:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸