My Private Site
Approved changes feed: RSS · Atom
cpe:2.3:a:zatzlabs:my_private_site:*:*:*:*:*:wordpress:*:*part: a version: * update: *
| Vendor | Zatzlabs (84aeb62f-ba3c-5415-9623-535219ad8c8f) |
|---|---|
| Product | My Private Site (d92d2af9-28d9-53a5-af44-c6e4c33acb35) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | wordpress |
| 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-2024-0978 |
vulnerable | 2026-06-08 06:22:03.266640 |
My Private Site <= 3.0.14 - Improper Access Control to Sensitive Information Exposure via REST API
MEDIUM (5.3)
The My Private Site plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 3.0.14 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's site privacy feature and view restricted page and post content.
Published: 2024-02-20T18:56:37.577Z
Updated: 2026-04-08T17:10:22.249Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-1627 |
vulnerable | 2026-06-08 05:39:13.602320 |
My Private Site < 3.0.8 - Arbitrary Settings Update via CSRF
The My Private Site WordPress plugin before 3.0.8 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack
Published: 2022-06-27T08:57:17.000Z
Updated: 2024-08-03T00:10:03.670Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.