Security readout for executives and security teams
Plain-English summary
Joro versions before 1.1.1 can let a malicious webpage install and execute a native plugin through Joro’s unauthenticated local API. An operator only needs to visit the page while Joro’s default proxy mode is running. The resulting code runs with the operator’s privileges, potentially compromising their workstation and accessible data.
Executive priority
Treat this as an urgent workstation-compromise risk for teams using Joro. Immediately identify installations and upgrade anything earlier than 1.1.1. Prioritize operators with access to sensitive testing environments, credentials, source code, or client systems. Current sources do not establish exploitation in the wild.
Technical view
The default proxy exposes an unauthenticated API on 127.0.0.1:9090 with wildcard CORS. Cross-origin JavaScript can submit CORS-safelisted multipart/form-data requests without preflight, reaching plugin-upload and restart functionality. Uploaded native plugins execute when loaded. The issue affects BishopFox Joro versions earlier than 1.1.1 and is fixed in 1.1.1.
Likely exposure
Exposure is limited to systems running Joro earlier than 1.1.1, particularly in default proxy mode, when an operator visits attacker-controlled or compromised web content. Binding the API to localhost does not prevent browser-based cross-origin access. The supplied sources do not quantify deployment prevalence.
Exploitation context
Successful exploitation requires user interaction: the Joro operator must visit a malicious page while the vulnerable local service is reachable. No credentials or prior privileges are required. The supplied bundle states that this CVE is not in KEV and provides no evidence of active exploitation.
Researcher notes
CVSS 3.1 is 9.6 with network reachability, low complexity, no privileges, required user interaction, changed scope, and high confidentiality, integrity, and availability impact. Listed weakness classes cover missing authentication, cross-site request forgery, unrestricted upload, and permissive cross-origin policy. Public evidence confirms the vulnerability and patch but not active exploitation or deployment prevalence.
Mitigation direction
- Upgrade BishopFox Joro to version 1.1.1 or later.
- Follow the vendor advisory and release guidance for the patched version.
- Until upgraded, avoid running the vulnerable default proxy mode while browsing untrusted content.
- Investigate affected workstations for unexpected plugins or suspicious activity under the operator’s account.
Validation and detection
- Inventory systems running BishopFox Joro and record each installed version.
- Confirm every installation reports version 1.1.1 or later.
- Identify whether pre-1.1.1 installations used default proxy mode on port 9090.
- Review affected systems for unrecognized plugins and unexpected restarts.
- Verify the updated deployment no longer exhibits the advisory’s unauthenticated wildcard-CORS behavior.
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-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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 lookupCWE-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCWE-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 lookupCWE-942: 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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53649 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
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A: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:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H2.86GitHub_MVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A: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://github.com/BishopFox/joro/security/advisories/GHSA-xqhv-chqm-fhccCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/BishopFox/joro/releases/tag/1.1.1CVE reference, GitHub_M · x_refsource_MISC
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.