Security readout for executives and security teams
Plain-English summary
A WordPress booking plugin has a CSRF flaw. If a site user is tricked into interacting with attacker-controlled content, unintended low-integrity changes may occur. Public sources rate this medium, with no confidentiality or availability impact listed.
Executive priority
Treat as a moderate WordPress application risk. Prioritize sites that use the booking workflow for revenue, customer scheduling, or administrative operations, especially if no fixed release is confirmed.
Technical view
CVE-2023-45270 is CWE-352 CSRF in PINPOINT.WORLD Pinpoint Booking System WordPress plugin <= 2.9.9.4.0. CVSS 3.1 score is 4.3: network reachable, low complexity, no attacker privileges, user interaction required, integrity impact low.
Likely exposure
Exposure appears limited to WordPress sites running Pinpoint Booking System plugin version 2.9.9.4.0 or earlier. The source bundle does not identify affected endpoints, CPEs, or a fixed version.
Exploitation context
No CISA KEV listing is provided, and the cited sources do not report active exploitation. The CVSS vector indicates exploitation requires user interaction and can affect integrity only.
Researcher notes
Public evidence is sparse. The record confirms CSRF, affected plugin family, vulnerable version boundary, CWE, and CVSS. It does not provide endpoint details, proof-of-concept status, exploit telemetry, or confirmed remediation version.
Mitigation direction
- Inventory WordPress sites using the Pinpoint Booking System plugin.
- Check vendor and Patchstack guidance for a fixed plugin release.
- Upgrade if a fixed version is available from trusted channels.
- Disable the plugin where business use does not justify exposure.
- Limit WordPress administrative access to trusted users.
Validation and detection
- Confirm whether the booking-system plugin is installed on WordPress assets.
- Record the installed plugin version and compare it with <= 2.9.9.4.0.
- Review vendor or Patchstack advisories for remediation status.
- Check change logs or security advisories before accepting an update as fixed.
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-45270 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:N/UI:R/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:N/UI:R/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:N/UI:R/S:U/C:N/I:L/A:N
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.