Unauthenticated log disclosure via publicly accessible file
Published Nov 23, 2023 · Updated Apr 28, 2026
Sensitive data exposure in StellarWP Restrict Content 3.2.7 and earlier allows remote attackers to read plugin logs without authentication. Patchstack identifies the log file as the exposure locus, but its advisory and the upstream release notes do not disclose the faulty access-control operation. No account or user interaction is required; the documented impact is limited to confidentiality, and the exposed fields are not publicly specified.
Summary
What happened
Sensitive data exposure in StellarWP Restrict Content 3.2.7 and earlier allows remote attackers to read plugin logs without authentication. Patchstack identifies the log file as the exposure locus, but its advisory and the upstream release notes do not disclose the faulty access-control operation. No account or user interaction is required; the documented impact is limited to confidentiality, and the exposed fields are not publicly specified.
The record
- CVE
- CVE-2023-47668
- Published
- Nov 23, 2023
- Updated
- Apr 28, 2026
- Vendor
- Liquid Web
- Product
- Restrict Content
- Classifications
- CWE-200, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 23, 2023CVE publishedPublication date reported by the CVE source.
- Apr 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=3.2.7 changes=[{"at":"3.2.8","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo