CVE-2023-7074 is a CSRF flaw in the WP Social Bookmark Menu WordPress plugin through version 1.2. The record scores it 8.8 (High), while WPScan scores it 4.3 (medium). WPScan lists no known fix, so remove the plugin or replace it.
What's affected
The record lists WP Social Bookmark Menu through version 1.2. WPScan says there is no known fix. The two sources disagree on severity: the NVD record gives CVSS 8.8 High and WPScan gives 4.3 medium. This post reports both.
The flaw is the lack of a CSRF check when the plugin updates its settings. A logged-in administrator can be tricked into changing them.
How to check if you're exposed
Run these from your WordPress root with WP-CLI. They only read.
wp plugin list --fields=name,status,version,update
wp plugin get wp-social-bookmark-menu --field=version
Any installed copy is affected, since no fixed release is listed. If WP-CLI is not available, open Plugins in the dashboard and read the version under the plugin name. Also check staging copies, old backups restored to test sites, and multisite networks, where the plugin may be installed on only some sites.
What to do now
- Deactivate and delete the plugin. WPScan lists no fix.
- Review the menu and social links the plugin produced, and restore the content you want by hand.
- Use a separate browser profile for administration and log out when finished.
- Prefer plugins that are maintained and tested with current WordPress releases.
Why it matters
The description says there is no CSRF check when updating settings. A hostile page can submit the form in an administrator's logged-in browser. The record tags CWE-352. Settings changes on a menu plugin may look minor, but plugins that print stored values into pages can turn a forged change into persistent script content.
Cross-site request forgery works because the browser attaches a logged-in user's cookies to every request, including ones started by another site. If a settings form does not require a secret token that only the real page knows, a third-party page can cause the logged-in user's browser to submit it. The attacker never needs the password, only a moment of the victim's attention.
Patch priority depends on who can reach the flaw. Issues open to anonymous visitors come first, then issues that need a low-privilege account, then issues that need an administrator. Use the access level in the description to place this item in your queue, and write down the date you updated so you can answer later when someone asks whether a given site was exposed.
Weakness class in the record: CWE-352 (Cross-Site Request Forgery).
Quick check
How do nonces stop CSRF?
A nonce is a one-time secret embedded in the real form. A hostile page cannot read it, so a forged request lacks it and is rejected.
How do I find every site that runs this plugin?
Check your hosting dashboards and any site management tool, and run the WP-CLI commands above on each install. Agencies and hosts often forget staging copies and sites inherited from clients.
Sources
Last reviewed: 19 October 2026.
