Security readout for executives and security teams
Plain-English summary
CVE-2023-7198 affects the WP Dashboard Notes WordPress plugin before 1.0.11. An authenticated site user could delete private dashboard notes belonging to other accounts, causing unauthorized data loss and privacy impact within WordPress admin workflows.
Executive priority
Treat as a scheduled WordPress maintenance fix, not an emergency. Prioritize faster where many users have dashboard access or private notes support operational workflows.
Technical view
The issue is an insecure direct object reference in the plugin's post_id handling. A logged-in user could target note objects they do not own and delete private notes. The CVSS 3.1 score is 4.3, reflecting low attack complexity, required authentication, and low integrity impact.
Likely exposure
Exposure is limited to WordPress sites running WP Dashboard Notes versions before 1.0.11 with users who can authenticate to the site dashboard.
Exploitation context
The source bundle includes a WPScan vulnerability entry tagged as exploit, but it does not establish active exploitation. The CVE is not listed as KEV in the provided data.
Researcher notes
The affected vendor metadata is sparse, but the description clearly identifies WP Dashboard Notes before 1.0.11. Evidence supports an authenticated IDOR with integrity impact only; no source in the bundle confirms real-world active exploitation.
Mitigation direction
- Upgrade WP Dashboard Notes to version 1.0.11 or later.
- Disable or remove the plugin if it is not required.
- Limit dashboard accounts to trusted users until upgraded.
- Review vendor and WPScan guidance for any additional remediation notes.
Validation and detection
- Inventory WordPress sites for WP Dashboard Notes installations.
- Confirm installed plugin versions are not older than 1.0.11.
- Review WordPress user accounts with dashboard access.
- In staging, verify non-owner users cannot delete another user's private notes.
- Check available audit logs for unexpected note deletion activity.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-7198 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
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:L/UI:N/S:U/C:N/I:L/A:N2.81.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/75fbee63-d622-441f-8675-082907b0b1e6/CVE reference · exploit, vdb-entry
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
