Security readout for executives and security teams
Plain-English summary
CommentTweets for WordPress through version 0.6 can let an attacker trick a logged-in user into changing plugin settings. The attack depends on user interaction, but the attacker does not need a WordPress account. The source bundle does not identify a fixed version.
Executive priority
Prioritize remediation for WordPress sites using CommentTweets, especially externally managed or business-critical sites. No active exploitation is confirmed, but public exploit information and high impact justify prompt action.
Technical view
The plugin lacks CSRF checks in some settings update paths. CVSS 3.1 scores it 8.8 with network attack vector, low complexity, no attacker privileges, and required user interaction. Impact is rated high for confidentiality, integrity, and availability.
Likely exposure
Exposure is limited to WordPress sites running the CommentTweets plugin through 0.6. Risk is highest where privileged users remain logged in while browsing external content.
Exploitation context
The source bundle marks WPScan with an exploit tag, but KEV is false and no cited source states active exploitation. Treat this as publicly documented exploitability, not confirmed in-the-wild exploitation.
Researcher notes
Evidence confirms CWE-352 CSRF in settings update behavior, but the bundle does not name exact affected endpoints, a fixed version, or vendor mitigation. Avoid assuming broader WordPress compromise without local validation.
Mitigation direction
- Identify whether CommentTweets is installed and its version.
- Disable or remove CommentTweets if version is 0.6 or older.
- Check vendor, WordPress plugin, and WPScan guidance for a fixed release.
- Limit administrator browsing from authenticated WordPress sessions.
- Review recent plugin setting changes for unexpected modifications.
Validation and detection
- Inventory WordPress plugins across managed sites.
- Confirm whether CommentTweets version is 0.6 or older.
- Review administrative audit logs for unexpected settings changes.
- Check whether plugin settings pages enforce CSRF protection.
- Document whether a vendor-supported fixed version is available.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-6845 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/cbdaf158-f277-4be4-b022-68d18dae4c55CVE reference · exploit, vdb-entry
- https://magos-securitas.com/txt/2023-6845CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.