Skip to content
Fencer Vulns
high 8.8

CVE-2023-2833 in the critical feed json

ReviewX <= 1.6.13 - Arbitrary Usermeta Update to Authenticated (Subscriber+) Privilege Escalation

published 2023-06-06 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-34284

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
17.5%
EPSS 17.5% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

The ReviewX plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.6.13 due to insufficient restriction on the 'rx_set_screen_options' function. This makes it possible for authenticated attackers, with minimal permissions such as a subscriber, to modify their user role by supplying the 'wp_screen_options[option]' and 'wp_screen_options[value]' parameters during a screen option update.

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
22 mo ago

Exploit prediction

17.48% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • wordfence.com https://www.wordfence.com/threat-intel/vulnerabilities/id/70e1d701-2cff-4793-9e4c-5b16a4038e8d?source=cve referenced PoC, tagged "exploit" by a source, unverified
  • lana.codes https://lana.codes/lanavdb/a889c3ff-5df0-4d7e-951f-0b0406468efa/ referenced PoC, tagged "exploit" by a source, unverified
  • wordfence.com https://www.wordfence.com/blog/2023/05/wpdeveloper-addresses-privilege-escalation-vulnerability-in-reviewx-wordpress-plugin/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • reviewx ReviewX – Multi-Criteria Reviews for WooCommerce with Google Reviews & Schema

Classification

Weakness
  • CWE-269 Improper Privilege Management
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.