CVE-2026-110100: Jorani before 1.0.4 Missing Authorization and SSRF via Contracts::import()
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Jorani before 1.0.4 contains a missing authorization vulnerability in Contracts::import() that allows any authenticated user to import days off into any contract from an arbitrary URL. Attackers can submit a contract id and URL via POST to overwrite non-working-day calendars and abuse get_headers() and fopen() for server-side request forgery against internal hosts.
Description quoted from the CVE record (assigned by VulnCheck, published 2026-10-13).
Weakness: Missing Authorization
How it can be exploited
Exploitable over the network with low attack complexity with no special attack requirements needing low privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 3 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.002
low predicted chance of attack - VEDAS
- 0.987
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Jorani | before 1.0.4 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 1.0.4.
Vendor guidance:
- https://github.com/jorani/jorani/commit/59c403224401824489ec662934f71c90d27f614c (patch)
- Jorani v1.0.4 Release Notes (release-notes)
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-110100 Jorani - Server-Side Request Forgery Attempt. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-110100 Jorani - Server-Side Request Forgery Attempt"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"contracts/import"; nocase; fast_pattern; http.request_body; content:"url="; nocase; classtype:web-application-attack; reference:cve,CVE-2026-110100; reference:url,https://www.exploit.observer/?keyword=CVE-2026-110100&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=jorani&match=exact; sid:1084001; rev:1;)
CVE-2026-110100.rules on GitHub
References
Vendor advisories and patches
- https://github.com/jorani/jorani/commit/59c403224401824489ec662934f71c90d27f614c (patch)
- Jorani v1.0.4 Release Notes (release-notes)
Technical analysis and advisories
- https://github.com/jorani/jorani/issues/426 (issue-tracking, technical-description)
- https://github.com/jorani/jorani/blob/v1.0.2/application/controllers/Contracts.php#L358-L375 (technical-description)
- VulnCheck Advisory: Jorani before 1.0.4 Missing Authorization and SSRF via Contracts::import() (third-party-advisory)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
