LiveActive security incident?Get immediate response
CVE Record

CVE-2026-2290: Post Affiliate Pro <= 1.28.0 - Authenticated (Administrator+) Server-Side Request Forgery via 'Post Affiliate Pro URL' Field

The Post Affiliate Pro plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.28.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.

LowCVSS 3.8Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2026-2290 affects the Post Affiliate Pro WordPress plugin through version 1.28.0. A logged-in WordPress administrator can make the server send outbound web requests and view returned content. Business urgency is limited because administrator access is required, but impact can matter on sensitive internal networks.

Executive priority

Handle through normal vulnerability management unless administrator accounts are weak, shared, or suspected compromised. Prioritize higher if WordPress servers can reach internal services or sensitive metadata endpoints.

Technical view

This is a CWE-918 server-side request forgery in the plugin’s “Post Affiliate Pro URL” field. The report states Administrator-level users can trigger arbitrary outbound requests from the WordPress application and read response content. CVSS is 3.8 low, with network attack vector and high privileges required.

Likely exposure

Exposure is limited to WordPress sites running Post Affiliate Pro up to and including 1.28.0 where untrusted or compromised administrator accounts exist.

Exploitation context

The source bundle says exploitation was confirmed by observing response data from an external Collaborator endpoint. There is no KEV listing and no cited evidence of active exploitation in the wild.

Researcher notes

The provided sources identify the vulnerable field and code reference, but do not name a fixed version or vendor mitigation. Treat remediation status as incomplete until confirmed through vendor or WordPress plugin repository guidance.

Mitigation direction

  • Inventory WordPress sites for the Post Affiliate Pro plugin and version.
  • Restrict WordPress administrator access to trusted users only.
  • Review vendor or WordPress plugin guidance for an updated fixed version.
  • Monitor outbound web requests from affected WordPress servers.

Validation and detection

  • Confirm whether Post Affiliate Pro is installed on each WordPress site.
  • Check whether the installed version is 1.28.0 or earlier.
  • Review administrator account list for unnecessary or risky access.
  • Check logs for unusual outbound requests from WordPress servers.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-918: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Cloud metadata behavior lookup

The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-2290 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.8CVSS 3.1LowCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N1.22.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.8Low
CVSS 3.1 vector shape for CVE-2026-2290Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
jurajsimPost Affiliate Pro0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-918 · source CWE mapping

Server-Side Request Forgery (SSRF)

Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.