Security readout for executives and security teams
Plain-English summary
A WordPress plugin allowed administrators to save unsafe settings that could later run script in browsers. This mainly matters where admins should not be able to add raw HTML, such as multisite, because the flaw bypasses that restriction.
Executive priority
Treat this as a targeted cleanup item, not an emergency, unless affected multisite environments delegate admin access broadly. Prioritize plugin inventory and update confirmation because the issue undermines intended content restrictions.
Technical view
Call Now Accessibility Button before 1.1 insufficiently sanitized and escaped some settings, enabling admin-level stored XSS when unfiltered_html is disallowed. The issue maps to CWE-79. Affected-version metadata is limited, so confirm exposure by installed plugin version.
Likely exposure
Exposure is limited to WordPress sites running Call Now Accessibility Button before 1.1, especially multisite or restricted-admin environments. Sites not using the plugin, or updated to 1.1 or later, are not shown as affected by the bundle.
Exploitation context
The bundle cites WPScan and includes an exploit tag, but provides no exploit details and CISA KEV is false. There is no source-backed evidence here of active exploitation in the wild.
Researcher notes
Primary evidence is the CVE description and WPScan reference. No CVSS score is provided in the bundle. The vulnerability requires high privileges, but stored XSS may still matter where unfiltered_html is intentionally disabled.
Mitigation direction
- Update Call Now Accessibility Button to version 1.1 or later if installed.
- Check vendor and WPScan guidance for any additional remediation details.
- Remove the plugin if it is unused or no longer business-critical.
- Review multisite administrator permissions and plugin settings ownership.
Validation and detection
- Inventory WordPress sites for the Call Now Accessibility Button plugin.
- Confirm installed plugin versions are 1.1 or later.
- Review plugin settings for unexpected script-like content.
- Check security logs for suspicious administrator setting changes.
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-2635 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/81b89613-18d0-4c13-84e3-9e2e1802fd7cCVE 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.