Skip to content
Fencer Vulns
high 7.5

CVE-2023-2916 in the critical feed json

InfiniteWP Client <= 1.11.1 - Authenticated (Subscriber+) Sensitive Information Exposure

published 2023-08-15 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-34362

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

Summary

The InfiniteWP Client plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.11.1 via the 'admin_notice' function. This can allow authenticated attackers with subscriber-level permissions or above to extract sensitive data including configuration. It can only be exploited if the plugin has not been configured yet. If combined with another arbitrary plugin installation and activation vulnerability, it may be possible to connect a site to InfiniteWP which would make remote management possible and allow for elevation of privileges.

Patch / fix

  • revmakx infinitewp_client 1.12.1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

23.99% 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/aa157c80-447f-4406-9e49-9cc6208b7b19?source=cve referenced PoC, tagged "exploit" by a source, unverified
  • plugins.trac.wordpress.org https://plugins.trac.wordpress.org/browser/iwp-client/tags/1.11.1/core.class.php#L365 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected products

  • revmakx InfiniteWP Client

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-668 Exposure of Resource to Wrong Sphere
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.