dbcve.org
Joomla\!Application · Joomla

CVE-2023-23750

MEDIUM · 6.3 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to after 4.2.6 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in Joomla! 4.0.0 through 4.2.6. A missing token check causes a CSRF vulnerability in the handling of post-installation messages.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Cross-Site Request Forgery (CSRF) vulnerability exists in Joomla! 4.0.0 through 4.2.6 due to a missing anti-CSRF token validation in the post-installation message handling component. This allows attackers to potentially trick authenticated administrators into unknowingly executing unintended administrative actions through maliciously crafted requests.

MitigationUpgrade Joomla! to version 4.2.7 or later, which includes the proper token validation fix for the post-installation message handler.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Joomla\!Application
Affected:>= 4.0.0, <= 4.2.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Joomla version
    Log into the Joomla administrator dashboard and navigate to System > Information, or check the version.xml file in your Joomla installation root. Compare this version number against the affected range of 4.0.0 through 4.2.6.
    Affected if The installed version falls within 4.0.0 to 4.2.6 inclusive.
  2. Verify administrator access exists
    Check whether any user accounts with Super User or Administrator privileges exist in your Joomla installation. This can be done via the Users component in the administrator panel or by querying the #__users table in the database.
    Affected if There are active administrator or Super User accounts in the system.
  3. Confirm post-installation message handler is accessible
    Access the post-installation message handler component via the Joomla administrator panel (typically under System > Post-installation Messages) or by attempting to access the relevant API endpoint. This component must be reachable for the CSRF vulnerability to be exploitable.
    Affected if The post-installation message component is accessible to authenticated administrators.

You are affected if your Joomla version is between 4.0.0 and 4.2.6 and you have administrator accounts with access to the post-installation message handling component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 4.2.6
Interim mitigation

Upgrade Joomla! to version 4.2.7 or later, which includes the proper token validation fix for the post-installation message handler.

Recommended fix High confidence

Joomla! 4.2.7 or later

  1. 1. Back up your Joomla! 4.x installation and database before upgrading.
  2. 2. Download Joomla! 4.2.7 or later from the official Joomla! download page (https://downloads.joomla.org/).
  3. 3. Use the Joomla! Update component within your admin dashboard to install the update, or replace the core files manually following Joomla's upgrade documentation.
  4. 4. After upgrading, verify the admin interface loads correctly and test that post-installation messages function properly.
  5. 5. Confirm the update was successful by checking the Joomla version in System > Information.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Joomla\! Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23750 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23750 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data