LiveActive security incident?Get immediate response
CVE Record

CVE-2026-48901: Joomla! Core - [20260517] - Incorrect Cache Key Construction for InputFilter objects

The InputFilter::getInstance() method omitted a security sensitive parameter from the instance cache key.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-48901 affects Joomla! CMS. A Joomla core caching issue can cause security-sensitive InputFilter settings to be reused incorrectly. The published severity is high, with potential confidentiality impact. Organizations running affected Joomla versions should treat this as a priority patch-validation item, especially for public websites.

Executive priority

High priority for organizations operating Joomla websites, especially public-facing properties. Patch planning should start promptly, but current sources do not support claims of active exploitation.

Technical view

Joomla! reports that InputFilter::getInstance() omitted a security-sensitive parameter from its instance cache key. Affected versions are Joomla! CMS 4.0.0 through 5.4.5 and 6.0.0 through 6.1.0. CVSS 3.1 is 7.5: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, high confidentiality impact.

Likely exposure

Exposure is most relevant to internet-facing Joomla! CMS sites in the affected version ranges. The CVSS vector indicates remote unauthenticated reachability, but the provided sources do not describe specific vulnerable routes, configurations, or required extensions.

Exploitation context

No cited source or KEV listing indicates active exploitation. Public details are limited to the Joomla advisory and CVE metadata. The risk is still material because the issue is remote, low complexity, and can affect confidentiality according to CVSS.

Researcher notes

The root issue is cache-key construction for InputFilter instances. CWE is listed as CWE-524. Public material does not provide exploit mechanics, affected call paths, or proof-of-concept details. Avoid assuming exploitability beyond the CVSS and vendor description.

Mitigation direction

  • Inventory Joomla! CMS versions across public and internal sites.
  • Prioritize sites running 4.0.0-5.4.5 or 6.0.0-6.1.0.
  • Follow the Joomla advisory for the corrected release or official mitigation.
  • Back up sites before applying Joomla core updates.
  • Review access logs for unusual activity after remediation.

Validation and detection

  • Confirm Joomla! CMS version from administrative inventory or site records.
  • Check whether each instance falls in the affected version ranges.
  • Verify remediation against the Joomla vendor advisory.
  • Document any unsupported or delayed-upgrade Joomla instances.
  • Monitor Joomla security center updates for added technical guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-524: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-48901 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-48901Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Joomla! ProjectJoomla! CMS4.0.0-5.4.5, 6.0.0-6.1.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-524 · source CWE mapping

Use of Cache Containing Sensitive Information

Use of Cache Containing Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.