CVE-2025-45314: HortusFox Stored XSS in Calendar endpoint

CVE-2025-45314 · Severity: medium · CVSS 6.1 · Published 2025-08-13

HortusFox, a self-hosted plant management and tracking system, contains a security vulnerability in its calendar feature. An attacker can create a calendar event with a malicious name that, when saved, executes hidden code in the browsers of other users who view the system's chat or dashboard. This could allow an attacker to hijack user sessions, steal sensitive information, or perform actions on behalf of other users, including administrators.

Technologies: Hortusfox. Vendors: Hortusfox.

Quick answers

Is CVE-2025-45314 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-45314 being exploited in the wild.
How severe is CVE-2025-45314?
Medium severity, with a CVSS score of 6.1, published 13 August 2025.
Which products and versions are affected?
Daniel Brendel Hortusfox-Web 4.4.
Is there a fix for CVE-2025-45314?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2025-45314 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2025-45314?
Check whether you run Daniel Brendel Hortusfox-Web or Hortusfox at an affected version. 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 stored Cross-Site Scripting (XSS) vulnerability exists in the 'addedCalendarItem' function within the Calendar module of hortusfox-web v4.4. The vulnerability arises because the '$name' parameter is interpolated into a localization string and subsequently passed to the 'addToChat' function without proper sanitization or output encoding. The 'addToChat' function performs a raw SQL INSERT into the database, and the malicious payload is later rendered unescaped in the chat UI. An attacker can exploit this by creating a calendar event with a malicious name (e.g., containing <script> or <img> tags with onerror attributes). When any user, including administrators, views the chat or logs in, the payload executes in their browser context, potentially leading to session hijacking or privilege escalation.

Affected products

  • Daniel Brendel hortusfox-web 4.4

Timeline

  • 2025-08-13: disclosed: Initial disclosure date
  • 2025-08-13: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.