Security readout for executives and security teams
Plain-English summary
A critical flaw in the Joomla J-BusinessDirectory extension could let an unauthenticated remote attacker upload or delete files outside intended directories. Successful abuse could compromise the website, alter data, expose sensitive information, or disrupt service. Only versions 1.0.0 through 6.2.2 are identified as affected.
Executive priority
Treat as an immediate remediation priority for Internet-facing systems. Identify affected installations, upgrade or isolate them, and investigate for unauthorized file changes. The potential impact spans confidentiality, integrity, availability, and downstream systems, although active exploitation is not established by the supplied evidence.
Technical view
Upload and removal handlers accepted a client-controlled root path, allowed traversal into component site or administrator trees, lacked path-containment enforcement, and applied a weak extension check. CSRF protection was also absent. The supplied CVSS 4.0 vector rates the issue 10.0, with network access, low complexity, no privileges, and no user interaction.
Likely exposure
Internet-accessible Joomla sites running J-BusinessDirectory versions 1.0.0 through 6.2.2 should be treated as exposed. The source bundle does not identify affected configurations, required feature settings, or compensating controls that reliably prevent exploitation.
Exploitation context
The vulnerability is remotely reachable and requires neither authentication nor user interaction according to the supplied CVSS vector. Arbitrary upload and deletion could enable broad compromise. The CVE is not listed as KEV in the source bundle, and no cited source establishes active exploitation or public exploit availability.
Researcher notes
The risk arises from combining uncontrolled path selection, missing containment checks, weak extension validation, and absent CSRF tokens. The supplied material does not provide handler names, affected endpoints, forensic indicators, patch details, or evidence of exploitation. Validation should remain non-destructive and focus on versioning, logs, file integrity, and vendor guidance.
Mitigation direction
- Upgrade J-BusinessDirectory to version 6.2.3 or a later vendor-supported release.
- Disable or remove the extension until upgrading if immediate remediation is impossible.
- Restrict public access to the affected Joomla site while remediation is pending.
- Back up the site and database before remediation or forensic work.
- Check CMSJunkie guidance for additional fixes or configuration requirements.
Validation and detection
- Inventory Joomla sites and record every installed J-BusinessDirectory version.
- Confirm no deployed instance remains on versions 1.0.0 through 6.2.2.
- Review web logs for unusual upload, removal, or path-related requests.
- Compare component files against trusted backups or known-good release packages.
- Inspect site and administrator trees for unexpected or recently modified files.
- Verify the extension remains functional after upgrading without weakening access controls.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-75949 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 10 (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:H/SI:H/SA:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——JoomlaVulnerability scoring details
Base CVSS 4.0 score
10CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cmsjunkie.com/CVE reference, Joomla · product
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.