The Uix UserCenter WordPress plugin through 1.0.3 does not verify that the account being modified through an unauthenticated profile-update action belongs to the requester, and it authenticates that action with a token whose signing key is hardcoded and identical across every install, allowing unauthenticated attackers to forge a token for any user, overwrite an administrator's email and password, and take over the account.
CVE-2026-16259
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 30, 2026
Advisory Details (1)
Auto-updated Aug 30, 2026Uix UserCenter <= 1.0.3 – Unauthenticated Privilege Escalation | CVE 2026-16259 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/e551128c-c9b1-4e6a-a2aa-92830b7a4887/Vendor Advisories for CVE-2026-16259(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 05:21 UTCEG score recompute
- 2026-08-30 05:21 UTCGHSA enrichment
- 2026-08-30 01:30 UTCEG score recompute
- 2026-08-30 01:30 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 01:09 UTCEG score recompute▲ 9.80
- 2026-08-30 01:09 UTCGHSA enrichment
- 2026-08-30 01:08 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-08-29 06:21 UTCNVD update
- 2026-08-29 06:14 UTCEG score recompute
- 2026-08-29 06:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2026-16259?
When was CVE-2026-16259 disclosed?
Is CVE-2026-16259 actively exploited?
What is the CVSS score of CVE-2026-16259?
How do I remediate CVE-2026-16259?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16259
Is Your Infrastructure Affected by CVE-2026-16259?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.