LiveActive security incident?Get immediate response
CVE Record

CVE-2026-32520: WordPress RewardsWP plugin <= 1.0.4 - Privilege Escalation vulnerability

Incorrect Privilege Assignment vulnerability in Andrew Munro / AffiliateWP RewardsWP rewardswp allows Privilege Escalation.This issue affects RewardsWP: from n/a through <= 1.0.4.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-32520 is a critical privilege escalation flaw in the WordPress RewardsWP plugin through version 1.0.4. A vulnerable site could allow an attacker to gain higher privileges, risking site takeover, data exposure, and service disruption. The provided sources do not identify a fixed version or active exploitation.

Executive priority

High priority for any organization running RewardsWP on public WordPress sites. The issue is critical severity and may allow privilege escalation without authentication. Confirm exposure immediately and remove, disable, or update according to vendor guidance when available.

Technical view

The CVE describes CWE-266 Incorrect Privilege Assignment in Andrew Munro / AffiliateWP RewardsWP for WordPress, affecting versions through 1.0.4. CVSS 3.1 is 9.8: network-accessible, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to WordPress environments where the RewardsWP plugin is installed at version 1.0.4 or earlier. Because the CVSS vector is network-accessible and unauthenticated, internet-facing WordPress sites running the plugin should be prioritized.

Exploitation context

The source bundle does not show CISA KEV listing or confirm active exploitation. Patchstack and the CVE record identify the vulnerability class and severity, but no exploit details, indicators, or patched version are provided in the supplied sources.

Researcher notes

Public detail is limited in the supplied sources. The CVSS vector indicates unauthenticated network exploitation potential, but no exploit path or patch information is included. Avoid assuming exploitation until supported by KEV or a cited advisory update.

Mitigation direction

  • Identify all WordPress sites using the RewardsWP plugin.
  • If RewardsWP is not required, disable or remove it.
  • Check Patchstack and vendor channels for fixed version guidance.
  • Restrict administrative access to WordPress where operationally possible.
  • Increase monitoring for unexpected user or role changes.

Validation and detection

  • Confirm whether the rewardswp plugin is installed.
  • Record the installed RewardsWP version on each WordPress site.
  • Treat versions 1.0.4 and earlier as affected.
  • Review WordPress users and roles for unauthorized privilege changes.
  • Recheck vendor or Patchstack advisories for remediation updates.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-32520 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
2Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-32520Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Andrew Munro / AffiliateWPRewardsWPrewardswp, n/aunaffected
Weakness

CWE details

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

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.