CVE-2023-0581
Lcweb Privatecontent vulnerability
The PrivateContent plugin for WordPress is vulnerable to protection mechanism bypass due to the use of client side validation in versions up to, and including, 8.4.3. This is due to the plugin checking if an IP had been blocklist via client-side scripts rather than server-side. This makes it possible for unauthenticated attackers to bypass any login restrictions that may prevent a brute force attack.
Affected products
Privatecontent. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Lcweb Privatecontent runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- lcweb.it/privatecontent/changelog · Vendor Advisory
- www.wordfence.com/threat-intel/vulnerabilities/id/de73304e-7a28-4304-b1ed-2f6dd7738236 · Third Party Advisory
- www.wordfence.com/threat-intel/vulnerabilities/id/de73304e-7a28-4304-b1ed-2f6dd7738236?sou
- nvd.nist.gov/vuln/detail/CVE-2023-0581
- cve.org/CVERecord?id=CVE-2023-0581
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.