Post Affiliate Pro <= 1.29.0 - Authenticated (Administrator+) Server-Side Request Forgery via 'Post Affiliate Pro URL' Field
Strategic Overview
- Status
- Patched in 1.29.1
- Affected Plugin
- Post Affiliate Pro
- Affected Version
<= 1.29.0- CVSS
- 3.8Low
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-2290
At a glance
CVE-2026-2290 is a low-severity Server-Side Request Forgery (SSRF) vulnerability in the Post Affiliate Pro WordPress plugin, affecting versions <= 1.29.0. It carries a CVSS score of 3.8 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 1.29.1; sites on affected versions should update now. Disclosed March 2026, reported by Phap Nguyen Anh.
Vulnerability Overview
The Post Affiliate Pro plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.29.0. This makes it possible for authenticated attackers, with Administrator-level access, to make web requests to initiate arbitrary outbound requests from the application and read the returned response content. Successful exploitation was confirmed by receiving and observing response data from an external Collaborator endpoint.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Reaching this weakness in Post Affiliate Pro <= 1.29.0 takes an account at Administrator level or above. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Post Affiliate Pro the fix is 1.29.1: builds <= 1.29.0 are affected, anything from 1.29.1 onward is not.
Remediation
Update to version 1.29.1, or a newer patched version
How does WordSec protect against this?
An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Post Affiliate Pro 1.29.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Post Affiliate Pro
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C