LiveActive security incident?Get immediate response
CVE Record

CVE-2026-78080: Joomla Extension - feenders.de - Unauthenticated SQL injection in JooDatabase Lite < 5.1.0

Joomla Extension - feenders.de - Unauthenticated SQL injection in JooDatabase Lite < 5.1.0 - The cid parameter is used in queries without validation, allowing SQLi vectors.

CriticalCVSS 9.3Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

JooDatabase Lite versions before 5.1.0 allow an unauthenticated remote attacker to manipulate database queries through the cid parameter. A successful attack could expose or alter sensitive data and disrupt the affected Joomla site. Because no login or user interaction is required, internet-facing installations warrant urgent review.

Executive priority

Prioritize immediate identification and remediation of internet-facing installations. The combination of unauthenticated remote access, low attack complexity, and potentially complete data and service impact makes delay materially risky. Escalate any suspicious log evidence to incident response, but do not assume compromise without supporting evidence.

Technical view

CVE-2026-78080 is a CWE-89 SQL injection caused by using the cid parameter in database queries without validation. It affects JooDatabase Lite 1.0 through 5.0.0. The CVSS 4.0 score is 9.3, reflecting network reachability, low complexity, no privileges, no interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where an internet-accessible Joomla site runs JooDatabase Lite version 1.0 through 5.0.0 and exposes functionality processing cid. The bundle does not identify specific routes, deployment prevalence, or whether compensating controls reliably block attacks.

Exploitation context

The supplied record does not establish active exploitation, and the CVE is not identified as being in KEV. However, the vulnerable input is remotely reachable, requires no authentication or user interaction, and has low stated attack complexity. Treat suspected attempts as potentially serious while avoiding claims that exploitation is occurring.

Researcher notes

The source bundle identifies unsafe use of cid in queries but provides no affected route, code-level advisory, proof of concept, exploitation telemetry, or explicit patch notes. The title places the vulnerable boundary below 5.1.0, while the affected range is listed as 1.0–5.0.0. Validate vendor guidance before relying on version alone.

Mitigation direction

  • Inventory Joomla installations and identify every deployed JooDatabase Lite version.
  • Upgrade affected installations to version 5.1.0 or later after confirming vendor guidance and compatibility.
  • Restrict public access to affected functionality until upgrading if operationally feasible.
  • Review vendor guidance for additional remediation or configuration requirements.
  • Preserve relevant web, application, and database logs before remediation.

Validation and detection

  • Confirm the installed JooDatabase Lite version is 5.1.0 or later.
  • Verify no older extension copies remain in production, staging, backups, or deployment artifacts.
  • Review logs for suspicious cid requests and database errors indicating injection attempts.
  • Confirm affected functionality operates normally after remediation.
  • Use authorized, non-destructive security testing to verify cid is safely handled.
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 · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-78080 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
Critical
CVSS
9.3 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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: total

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
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Joomla

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-78080Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
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
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
joodb.feenders.deJooDatabase Lite extension for Joomla1.0-5.0.0unaffected
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.