CVE-2023-5561
WordPress does not properly restrict which user fields are searchable ...
Overview
Description
WordPress does not properly restrict which user fields are searchable via the REST API, allowing unauthenticated attackers to discern the email addresses of users who have published public posts on an affected website via an Oracle style attack
Source: OX vulnerability database
Severity
5.3 · MEDIUM
CVSS 3.1 base score, scored by NVD.
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected packages · 2
| Ecosystem | Package | Vulnerable | Fixed in |
|---|---|---|---|
| Bitnami | wordpress | >=4.7.0, <4.7.27>=4.8.0, <4.8.23>=4.9.0, <4.9.24>=5.0.0, <5.0.20>=5.1.0, <5.1.17+12 more | 4.7.274.8.234.9.245.0.205.1.17 |
| Bitnami | wordpress-multisite | >=4.7.0, <4.7.27>=4.8.0, <4.8.23>=4.9.0, <4.9.24>=5.0.0, <5.0.20>=5.1.0, <5.1.17+12 more | 4.7.274.8.234.9.245.0.205.1.17 |
Open a package to see all its vulnerabilities.
Operating systems · 6 fixes
debian 5 releases · 1 package
fixed 5
wordpress
| Release | Package | Fixed in |
|---|---|---|
| 10 | wordpress | 5.0.20+dfsg1-0+deb10u1 |
| 11 | wordpress | 5.7.11+dfsg1-0+deb11u1 |
| 12 | wordpress | 6.1.6+dfsg1-0+deb12u1 |
| 13 | wordpress | 6.3.2+dfsg1-1 |
| 14 | wordpress | 6.3.2+dfsg1-1 |
echo 1 release · 1 package
fixed 1
wordpress
| Release | Package | Fixed in |
|---|---|---|
| wordpress | 6.1.6+dfsg1-0+deb12u1 |
References
- lists.debian.org https://lists.debian.org/debian-lts-announce/2023/11/msg00014.html
- nvd.nist.gov https://nvd.nist.gov/vuln/detail/CVE-2023-5561
- wpscan.com https://wpscan.com/blog/email-leak-oracle-vulnerability-addressed-in-wordpress-6-3-2/
- wpscan.com https://wpscan.com/vulnerability/19380917-4c27-4095-abf1-eba6f913b441
OX Radar and Response Center
Find threats in your stack.
OX Radar can check high-priority threats, like critical package CVEs, against your context.
Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.