Joomla\!Application · Joomla
CVE-2015-7899
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 · uneditedThe com_content component in Joomla! 3.x before 3.4.5 does not properly check ACLs, which allows remote attackers to obtain sensitive information via unspecified vectors.
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 · moderate confidenceThe com_content component in Joomla! versions 3.x before 3.4.5 has an ACL (Access Control List) bypass vulnerability that allows remote attackers to access sensitive information without proper authorization checks.
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.2.0= 3.2.1= 3.2.2= 3.2.3= 3.2.4= 3.3.0= 3.3.1= 3.3.2= 3.3.3= 3.3.4= 3.4.0= 3.4.1CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/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.
-
Locate the Joomla installation directoryIdentify the web root directory where Joomla is installed. Look for typical Joomla files such as 'index.php', 'configuration.php', or the 'administrator' folder in the web root.Affected if Joomla is not present on the system, then this CVE does not apply.
-
Determine the installed Joomla versionCheck the version file typically found at /libraries/cms/version.php or review the manifest file in /administrator/manifests/files/joomla.xml. The version number is defined as a constant in these files.Affected if The exact version cannot be determined from the installation.
-
Compare the installed version against the affected rangeThe affected versions are: 3.2.0, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.3.0, 3.3.1, 3.3.2, 3.3.3, 3.3.4, 3.4.0, and 3.4.1. Match your installed version against this list.Affected if The installed version matches any version in the affected list (3.2.0 through 3.4.1).
-
Verify the com_content component is present and enabledCheck for the com_content component directory at /components/com_content/ and verify it is not disabled in the Joomla administrator components management or database #__extensions table.Affected if The com_content component is absent or explicitly disabled in the Joomla extension management.
A system is affected by this CVE if it is running Joomla versions 3.2.0 through 3.4.1 and the com_content component is installed and enabled.
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 dataUpgrade Joomla! to version 3.4.5 or later to apply the ACL fix.
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-2015-7899 — 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-2015-7899 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