CVE-2023-6845 is a CSRF flaw in the CommentTweets WordPress plugin through version 0.6. 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. Do not wait for a patch that may never arrive.
What's affected
The record lists CommentTweets through version 0.6. WPScan says there is no known fix. The two sources disagree on severity: the NVD record gives CVSS 8.8 High, and WPScan gives CVSS 4.3 medium. This post reports both and does not choose between them.
The plugin saves Twitter login details through a settings form that lacks CSRF checks, according to the WPScan entry.
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 commenttweets --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 if it is installed. WPScan lists no fix.
- If the plugin stored Twitter or X credentials, change them.
- Consider whether you still use comment-to-tweet features, and pick a maintained replacement if you do.
- Make a habit of removing abandoned plugins.
Why it matters
The description says the plugin lacks CSRF checks in some places. A settings page that changes saved credentials without a nonce can be triggered by a hostile web page while an administrator is logged in. The record tags CWE-352.
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
Why do two sources give different scores?
Scoring depends on assumptions about impact and privilege. When two respected sources differ, read the description and decide using your own exposure.
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.
