JustAppSec
Back to news

Access check flaw exposes Joomla webservice endpoints

1 min readPublished 01 Apr 2026Updated 01 Apr 2026Source: CVEProject (cvelistV5)

TL;DR — A High-severity access-control bug in Joomla’s web services can allow requests to reach webservice endpoints without the intended authorization checks.

What happened

Joomla is a widely used PHP-based content management system (CMS) for building and operating websites.

CVE-2026-23899 describes an improper access check in Joomla’s webservice endpoints, where a missing/incorrect access-control decision can result in unauthorized access to webservice endpoints.

The CVE record reports CVSS v4.0 base score 8.6 (High) with Privileges Required: High, and the Joomla Security Announcements entry marks Probability: Low. This is still a meaningful appsec signal: access-control regressions in API layers are a recurring source of data exposure and control-plane abuse, especially when webservice endpoints are internet-reachable.

Who is impacted

  • Joomla! CMS installations running affected versions:
    • 4.0.0 through 5.4.3
    • 6.0.0 through 6.0.3
  • Environments that have Joomla web services enabled/exposed, since the issue is specifically in webservice endpoints.
ComponentAffected versions (per vendor advisory)Patched versions (per vendor advisory)
Joomla! CMS4.0.0–5.4.3, 6.0.0–6.0.35.4.4, 6.0.4

What to do now

  • Follow vendor remediation guidance and apply the available fixed releases.
    • "Upgrade to version 5.4.4 or 6.0.4"

  • Inventory Joomla deployments (including container images and artifacts) and map them to the affected version ranges.
  • Review whether Joomla web services are enabled/exposed in production, and confirm that access controls for API/webservice routes match your intended authorization model.
  • If compromise or misuse is suspected, audit webservice/API access logs for unexpected callers, endpoint enumeration, and anomalous authorization patterns, then rotate credentials/tokens reachable by the impacted Joomla instance.

Content is AI-assisted and reviewed by our team, but issues may be missed and best practices evolve rapidly, send corrections to [email protected]. Always consult official documentation and validate key implementation decisions before making design or security choices.

Need help?Get in touch.