Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using the AI ChatBot plugin before 4.6.1. A trusted administrator could store JavaScript through plugin settings even when WordPress normally blocks unfiltered HTML. The main risk is malicious or compromised admin activity, not broad unauthenticated compromise.
Executive priority
Treat this as a targeted WordPress hardening issue. Prioritize affected sites with many administrators, delegated site management, or weak admin account controls. It is less urgent than unauthenticated remote code execution, but still worth remediating promptly.
Technical view
CVE-2023-3175 is a stored cross-site scripting issue caused by inadequate escaping of some AI ChatBot plugin settings before version 4.6.1. The source states high-privilege users, such as admins, can trigger XSS even when unfiltered_html is disallowed. CWE-79 applies. No CVSS score is provided.
Likely exposure
Exposure is limited to WordPress installations with AI ChatBot installed below 4.6.1, especially where multiple admins exist or admin accounts may be compromised.
Exploitation context
The WPScan reference is tagged as exploit, but the provided sources do not show CISA KEV listing or active exploitation evidence. Attack preconditions appear high-privilege, admin-level access.
Researcher notes
The bundle does not include CVSS details, vendor identity, or full exploit mechanics. The key confirmed facts are stored XSS, settings escaping failure, admin-plus prerequisite, affected versions before 4.6.1, and no KEV evidence.
Mitigation direction
- Upgrade AI ChatBot to version 4.6.1 or later.
- Review vendor and WPScan guidance for any additional remediation.
- Limit WordPress administrator access to trusted users only.
- Audit recent plugin setting changes for unexpected script content.
Validation and detection
- Inventory WordPress sites for the AI ChatBot plugin.
- Confirm installed plugin versions are 4.6.1 or later.
- Review admin user accounts for unnecessary or stale access.
- Check whether untrusted users hold high-privilege WordPress roles.
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-79: 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-3175 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/7643980b-eaa2-45d1-bd9d-9afae0943f43CVE 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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.