Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress WP Logo Showcase Responsive Slider and Carousel plugin through version 3.6. The reported issue is broken access control: an unauthenticated network attacker may be able to bypass authorization and make limited integrity-impacting changes. Public sources do not show active exploitation or a named fixed version.
Executive priority
Handle this as a moderate-priority WordPress plugin risk. It does not currently justify emergency response without exploitation evidence, but exposed sites using the plugin should be remediated promptly because unauthenticated integrity changes can affect public-facing content and trust.
Technical view
The issue is an authorization bypass through a user-controlled key in Essential Plugin's WP Logo Showcase Responsive Slider and Carousel, mapped to CWE-639. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges, no user interaction, unchanged scope, low integrity impact only.
Likely exposure
Exposure is limited to WordPress sites with the affected plugin installed at version 3.6 or earlier. Internet-facing WordPress sites are the main concern because the CVSS vector indicates unauthenticated network access. The source bundle does not identify affected endpoints, prevalence, or hosted-service exposure.
Exploitation context
The source bundle does not include proof-of-concept details, exploitation reports, or CISA KEV listing. Treat exploitation as unconfirmed. The impact described is limited to integrity, not confidentiality or availability, but unauthorized content or configuration changes could still create business risk.
Researcher notes
Public detail is sparse. The record identifies CWE-639 and a user-controlled key authorization bypass, but does not provide endpoint-level detail, exploit status, or a fixed release. Validation should focus on asset/version discovery, vendor guidance, and safe authorization testing without assuming undocumented exploit mechanics.
Mitigation direction
- Inventory WordPress sites for the affected plugin and version.
- Check the vendor and Patchstack entry for current remediation guidance.
- Update if a fixed version is available from trusted WordPress channels.
- Disable or remove the plugin where it is not required.
- Use WordPress least-privilege controls and monitoring as compensating measures.
Validation and detection
- Confirm whether the plugin slug is installed on each WordPress site.
- Record installed versions and flag version 3.6 or earlier.
- Review vendor or Patchstack status before declaring remediation complete.
- Check logs for unusual unauthenticated requests affecting plugin-managed content.
- Verify staging behavior prevents unauthorized changes to plugin-managed data.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior 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-40200 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:N/S:U/C:N/I:L/A:N3.91.4PatchstackVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.