My Private Site < 3.0.8 - Arbitrary Settings Update via CSRF
Priority LOW 20CWE-352Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352.
Summary
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
Why it matters now
EPSS 0.00429 37th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed My Private Site (Unknown): 3.0.8
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | My Private Site | 3.0.8 to before 3.0.8 | 3.0.8 | Patch available | CNA |
- My Private Site VendorUnknown Affected 3.0.8 to before 3.0.8 Fixed in 3.0.8 Patch available CNA
Remediation
- Fix · CNA My Private Site (Unknown) Fixed in 3.0.8
Timeline
- 2026-10-02 Threatist record created from CVE-2022-1627
- 2026-10-03 Alias added: GHSA-gpv9-46c5-35gc
References
More Zatzlabs My Private Site vulnerabilities
- TI-2024-00902 My Private Site <= 3.0.14 - Improper Access Control to Sensitive Information Exposure via REST API CVSS 3.1MEDIUM 5.3
Sources
- CVE-2022-1627 · CVE Program
- CVE-2022-1627 · NVD
- FIRST EPSS
- GHSA-gpv9-46c5-35gc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences