Joomla\!Application · Joomla
CVE-2019-7739
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.3. The "No Filtering" textfilter overrides child settings in the Global Configuration. This is intended behavior. However, it might be unexpected for the user because the configuration dialog lacks an additional message to explain this.
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 confidenceIn Joomla! before 3.9.3, the 'No Filtering' textfilter option in Global Configuration intentionally overrides child/lower-level settings. However, the configuration interface lacks an explanatory message alerting users to this behavior, potentially leading administrators to unknowingly disable important text filtering without understanding the implications.
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
>= 2.5.0, <= 3.9.2CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Identify the installed Joomla versionLog into the Joomla administrator panel and navigate to Help > System Information, or check the /libraries/cms/version/version.php file for the VERSION constantAffected if The version is between 2.5.0 and 3.9.2 inclusive
-
Access Global Configuration text filter settingsIn the Joomla admin panel, go to System > Global Configuration and locate the Text Filters tab (or Text Filtering section)Affected if This section is accessible and visible in the affected version range
-
Check the text filter setting valueIn the Text Filters tab, identify the filter type selected for the Super User or Public groups. Look for a setting labeled 'No Filtering' or similarAffected if The 'No Filtering' option is selected for any user group (especially Super Users or Public)
-
Verify database configuration storageQuery the Joomla database (typically the #__config table or similar configuration storage) for text_filter settings. The exact table depends on Joomla version (e.g., #__extensions for newer versions)Affected if The stored text filter configuration shows 'no_filter' or a value indicating filtering is disabled
You are affected if running Joomla! version 2.5.0 through 3.9.2 AND the Global Configuration has 'No Filtering' text filter enabled, which bypasses all content filtering without warning.
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 to Joomla! 3.9.3 or later. Alternatively, ensure administrators understand that selecting 'No Filtering' disables text filtering across all child configurations.
Fix this in Joomla\!
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7739 — 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-7739 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