Unauthenticated server-side request forgery
Published Apr 8, 2026 · Updated Apr 8, 2026
Server-side request forgery in Podigee WordPress Quick Publish 1.4.0 and earlier allows remote attackers to send server-side requests. Patchstack has not published the vulnerable endpoint or function, the attacker-controlled input, or the request-handling operation that fails to validate it. No authentication or user interaction is required, but exploitation depends on unspecified high-complexity conditions and produces limited cross-boundary data exposure or modification.
Summary
What happened
Server-side request forgery in Podigee WordPress Quick Publish 1.4.0 and earlier allows remote attackers to send server-side requests. Patchstack has not published the vulnerable endpoint or function, the attacker-controlled input, or the request-handling operation that fails to validate it. No authentication or user interaction is required, but exploitation depends on unspecified high-complexity conditions and produces limited cross-boundary data exposure or modification.
The record
- CVE
- CVE-2026-39695
- Published
- Apr 8, 2026
- Updated
- Apr 8, 2026
- Vendor
- Podigee
- Product
- Podigee WordPress Quick Publish
- Classifications
- CWE-918, CAPEC-664, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2026CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo