Security readout for executives and security teams
Plain-English summary
This CVE affects the WordPress Intrepidity component up to version 1.5.1. A malicious site could abuse a logged-in user’s browser to trigger an arbitrary file upload. That can threaten site confidentiality, integrity, and availability, but the provided sources do not show active exploitation or a named fixed version.
Executive priority
Treat this as a high-priority WordPress exposure where Intrepidity is installed. Prioritize internet-facing sites, confirm whether the component exists, and remove or update it based on vendor guidance.
Technical view
The vulnerability is CWE-352 CSRF with CVSS 3.1 score 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Sources describe arbitrary file upload in Shingo Intrepidity <= 1.5.1, though they inconsistently call it a theme and plugin. No exploit details or confirmed patch are provided.
Likely exposure
Exposure is limited to WordPress sites running Shingo Intrepidity at or below 1.5.1. The bundle does not provide CPEs, exact package metadata, or default affected status clarity, so asset verification is required.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The CVSS vector requires user interaction, consistent with CSRF, but the sources do not confirm exploitation in the wild, attacker tooling, or required victim role.
Researcher notes
Evidence supports CSRF leading to arbitrary file upload, but public details in the bundle are sparse. The theme/plugin inconsistency and missing fixed-version data reduce certainty. Avoid assuming exploitation or remediation beyond vendor/Patchstack guidance.
Mitigation direction
- Inventory WordPress sites for Intrepidity and confirm installed versions.
- Remove or disable Intrepidity if running version 1.5.1 or earlier.
- Check Patchstack and vendor guidance for a fixed release or official workaround.
- Replace the component if no supported fix is available.
- Review upload locations and recent file changes for suspicious additions.
Validation and detection
- Confirm whether Intrepidity is installed as a theme or plugin.
- Verify the installed version is greater than 1.5.1, if a fixed version exists.
- Check WordPress file upload areas for unexpected files.
- Review access and application logs around suspicious upload activity.
- Document source uncertainty around theme versus plugin naming.
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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell 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-27634 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
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.