WP Social Bookmark Menu <= 1.2 - Settings Update via CSRF
Priority HIGH 71CWE-352Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-352.
Summary
The WP SOCIAL BOOKMARK MENU WordPress plugin through 1.2 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
Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00329 26th percentileScored 2026-11-07
Public exploit Yes 2 exploit referencesTagged by the CNA and NVD
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | WP SOCIAL BOOKMARK MENU | up to 1.2 | — | No fix listed | CNA |
- WP SOCIAL BOOKMARK MENU VendorUnknown Affected up to 1.2 Fixed in — No fix listed CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:giovambattistafazioli:wp_social_bookmark_menu:*:*:*:*:*:wordpress:*:* | up to 1.2 | Vulnerable | Giovambattista Fazioli |
- cpe:2.3:a:giovambattistafazioli:wp_social_bookmark_menu:*:*:*:*:*:wordpress:*:* Versions up to 1.2 Vulnerable ·Giovambattista Fazioli
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2023-7074
- 2026-10-03 Alias added: GHSA-rm8m-jx8f-gg9f
References
Sources
- CVE-2023-7074 · CVE Program
- CVE-2023-7074 · NVD
- FIRST EPSS
- GHSA-rm8m-jx8f-gg9f · 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