Joomla\!Application · Joomla
CVE-2019-9713
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 · uneditedAn issue was discovered in Joomla! before 3.9.4. The sample data plugins lack ACL checks, allowing unauthorized access.
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 confidenceJoomla! before version 3.9.4 contains sample data plugins that do not perform Access Control List (ACL) checks. This allows unauthenticated or unauthorized users to access functionality that should be restricted based on user permissions, resulting in an authorization bypass vulnerability with CVSS 7.5 severity.
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
>= 3.8.0, < 3.9.4CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Joomla is installedCheck for Joomla installation directories (administrator, components, modules, plugins, libraries) or look for joomla.xml in the web root or administrator/manifests/files/joomla.xmlAffected if Joomla CMS is present on the server
-
Determine installed Joomla versionOpen administrator/manifests/files/joomla.xml and locate the <version> tag, or check libraries/cms/version/version.php for the $RELEASE or $DEV_LEVEL variablesAffected if The version cannot be determined or the file is missing
-
Compare version against affected rangeParse the version number from step 2 and compare: it must be greater than or equal to 3.8.0 AND less than 3.9.4Affected if Version is >= 3.8.0 AND < 3.9.4 (for example, 3.8.0, 3.8.1, 3.8.10, 3.9.0, 3.9.3)
-
Confirm sample data plugins existCheck the plugins directory for sample data related plugins (typically in /plugins/sampledata/) or inspect the Joomla admin panel under Extensions > Plugins for any plugin with 'sampledata' in the type or nameAffected if Sample data plugins are present in the installation (these are included by default in Joomla)
The environment is affected if Joomla version is 3.8.0 through 3.9.3 inclusive, and sample data plugins are present (which is the default configuration).
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data3.9.4
Upgrade Joomla! to version 3.9.4 or later. If immediate patching is not possible, disable or restrict access to the sample data plugins through web server configuration or other access controls until the update can be applied.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-9713 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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