Privatecontent
Approved changes feed: RSS · Atom
cpe:2.3:a:lcweb:privatecontent:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Lcweb (a6a6f2a1-0f89-5983-acea-b8e51c9b0357) |
|---|---|
| Product | Privatecontent (2d71febe-80f1-558b-a2cf-7da121acf286) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-57692 |
vulnerable | 2026-07-29 01:03:16.034091 |
WordPress PrivateContent plugin <= 9.9.2 - Privilege Escalation vulnerability
CRITICAL (9.8)
Incorrect Privilege Assignment vulnerability in LCweb PrivateContent allows Privilege Escalation.
This issue affects PrivateContent: from n/a through 9.9.2.
Published: 2026-07-01T13:34:09.184Z
Updated: 2026-07-01T14:25:49.078Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-0581 |
vulnerable | 2026-06-08 05:52:31.962972 |
PrivateContent <= 8.4.3 - Protection Mechanism Bypass
MEDIUM (5.3)
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.
Published: 2023-01-30T14:06:27.936Z
Updated: 2026-04-08T17:28:18.465Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.