Security readout for executives and security teams
Plain-English summary
WP Yelp Review Slider versions before 7.1 let a logged-in WordPress user with subscriber-level access reach a SQL injection flaw. Sites with public registration or many low-trust accounts have higher exposure. The provided sources do not show CISA KEV listing or confirmed active exploitation.
Executive priority
Treat this as urgent for public-facing WordPress sites using the plugin, particularly membership or customer portals. Prioritize inventory and upgrade.
Technical view
The plugin fails to sanitize and escape a parameter before using it in a SQL statement, creating CWE-89 SQL injection. The affected range is described as WP Yelp Review Slider before 7.1. The source bundle provides no CVSS score, payload details, or complete vendor advisory.
Likely exposure
WordPress sites running WP Yelp Review Slider before 7.1 are exposed, especially where subscriber accounts are easy to obtain.
Exploitation context
WPScan tags the issue with exploit availability, but the bundle does not provide active exploitation evidence. CISA KEV status is false.
Researcher notes
Evidence is limited to CVE and WPScan-style descriptions. Validate exposure by version and role model, not by assuming unauthenticated reachability or active exploitation.
Mitigation direction
- Upgrade WP Yelp Review Slider to version 7.1 or later.
- If upgrade timing is unclear, check current vendor or WordPress plugin guidance.
- Review whether public registration or low-trust subscriber accounts are enabled.
- Temporarily disable the plugin if upgrade or validation is not possible.
- Monitor WordPress database and admin activity for suspicious changes.
Validation and detection
- Inventory WordPress sites for the WP Yelp Review Slider plugin.
- Confirm the installed plugin version is 7.1 or later.
- Review user registration settings and subscriber account volume.
- Check security logs for suspicious authenticated requests to plugin functionality.
- Document remediation status for each affected WordPress instance.
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-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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 lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-0263 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/2b4a6459-3e49-4048-8a9f-d7bb350aa2f6CVE 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 Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.