Security readout for executives and security teams
Plain-English summary
OTWthemes Blog Manager Light for WordPress through version 1.20 has a CSRF vulnerability. An attacker could trick a user’s browser into sending an unintended request, causing limited integrity or availability impact. The sources do not identify active exploitation.
Executive priority
Treat as a moderate WordPress hygiene issue. Prioritize sites using the plugin, especially externally managed or high-value sites, but do not escalate as active exploitation without new evidence.
Technical view
CVE-2023-45102 is CWE-352 in the blog-manager-light WordPress plugin <= 1.20. CVSS 3.1 is 5.4 with network attack vector, low complexity, no attacker privileges, required user interaction, no confidentiality impact, and low integrity and availability impact.
Likely exposure
Exposure is limited to WordPress sites that installed OTWthemes Blog Manager Light at version 1.20 or earlier. The source bundle does not provide affected endpoint details or fixed-version evidence.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Abuse would require user interaction consistent with CSRF.
Researcher notes
Public details are sparse. The bundle names CSRF, plugin, version threshold, CVSS, CWE, and Patchstack reference, but not the vulnerable action, nonce behavior, proof, or fixed release.
Mitigation direction
- Inventory WordPress sites for the blog-manager-light plugin and its installed version.
- Check OTWthemes, WordPress plugin, or Patchstack guidance for an update or official mitigation.
- Disable or remove the plugin where it is not business-critical.
- Restrict administrative access and reinforce anti-CSRF controls where compensating controls are available.
Validation and detection
- Confirm whether Blog Manager Light is installed on each WordPress site.
- Record installed plugin versions and flag version 1.20 or earlier.
- Review vendor or Patchstack advisories for fixed-version status before closing remediation.
- Check security monitoring for unusual plugin-related administrative actions.
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-45102 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
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
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:N/I:L/A:L2.82.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
Source materials
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.