Security readout for executives and security teams
Plain-English summary
Joomla sites running 4.0.0 through 4.2.6 have a CSRF flaw in post-installation messages. If a user can be induced to interact with a malicious request, actions in that area may occur without the expected anti-CSRF token protection.
Executive priority
Treat this as a scheduled but real web application remediation item. It is not evidenced as actively exploited here, but exposed Joomla administrative workflows should be upgraded promptly because CSRF can convert user interaction into unauthorized changes.
Technical view
CVE-2023-23750 is CWE-352 in Joomla CMS 4.0.0-4.2.6. The issue is a missing token check in handling post-installation messages. CVSS 3.1 is 6.3 with network attack vector, low complexity, no privileges required, user interaction required, and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to Joomla CMS deployments in the 4.0.0-4.2.6 range. The source bundle does not identify affected extensions, hosting platforms, or configurations beyond Joomla core.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVSS vector indicates user interaction is required, consistent with CSRF risk rather than unauthenticated direct compromise.
Researcher notes
Evidence is narrow: affected range, CWE, CVSS, and vendor advisory are available. The bundle does not provide exploit details, patch notes, or exploitation telemetry. Validation should focus on version exposure and vendor-advised remediation, not proof-of-concept testing.
Mitigation direction
- Identify Joomla CMS instances running versions 4.0.0 through 4.2.6.
- Upgrade affected sites to a release outside the affected range after checking Joomla guidance.
- Limit administrative access to trusted networks where operationally feasible.
- Educate privileged users to avoid untrusted links while remediation is pending.
Validation and detection
- Inventory Joomla CMS versions across production, staging, and legacy sites.
- Confirm affected systems are not running 4.0.0 through 4.2.6 after remediation.
- Review Joomla vendor advisory for any updated remediation instructions.
- Check administrative activity around post-installation messages for unexpected 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-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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access 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-23750 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
- 6.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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:L/I:L/A:L2.83.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://developer.joomla.org/security-centre/890-20230101-core-csrf-within-post-installation-messages.htmlCVE reference · vendor-advisory
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.