Quick answers
- Is CVE-2026-35400 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35400 being exploited in the wild.
- How severe is CVE-2026-35400?
- Low severity, with a CVSS score of 3.5, published 8 April 2026.
- Which products and versions are affected?
- aces LORIS 20.0.0 to 27.0.2, 28.0.0.
- Is there a fix for CVE-2026-35400?
- A patch was published on 2026-04-08: Fixes released in versions 27.0.3 and 28.0.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35400 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-35400?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability in the LORIS publication module arises from the application incorrectly trusting a 'baseURL' parameter submitted via POST requests in the FileUpload.php component. Instead of using the internal, trusted configuration value, the 'notify' function uses the attacker-controlled input to construct URLs for email notifications (e.g., submission, edit, and review alerts). An authenticated attacker with publication module access can exploit this to conduct a Server-Side Request Forgery (SSRF) variant or phishing attack by injecting an external domain into the baseURL. This results in the system generating and sending legitimate-looking emails that direct recipients to an attacker-controlled site. The issue is resolved in versions 27.0.3 and 28.0.1 by removing the baseURL parameter from the notification logic.
Affected products
- aces LORIS 20.0.0 to 27.0.2, 28.0.0
Timeline
- 2026-04-08: advisory: GitHub Security Advisory published
- 2026-04-08: patched: Fixes released in versions 27.0.3 and 28.0.1