Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-113349 Overview
CVE-2026-113349 is a missing authorization vulnerability [CWE-639] in OpenCATS versions prior to 0.10.0. The flaw resides in the CalendarUI::onEditEvent() and CalendarUI::onDeleteEvent() functions within the calendar module. Authenticated users with EDIT or DELETE access can supply arbitrary eventID values to modify or delete calendar events belonging to other users, including non-public events restricted to their owner. The vulnerability stems from the absence of ownership checks before executing event mutations.
Critical Impact
Any authenticated OpenCATS user with calendar edit or delete privileges can tamper with or destroy other users' private calendar entries, undermining data integrity across the recruitment platform.
Affected Products
- OpenCATS applicant tracking system versions prior to 0.10.0
- Self-hosted OpenCATS deployments exposing the calendar module
- Any OpenCATS instance where multiple users share EDIT or DELETE access levels on contacts
Discovery Timeline
- 2026-10-20 - CVE-2026-113349 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-113349
Vulnerability Analysis
The vulnerability lives in the OpenCATS calendar module, specifically modules/calendar/CalendarUI.php. When a user triggers an edit or delete action, the handler accepts an eventID parameter from the request and passes it directly to the underlying Calendar class methods. The code performs no verification that the authenticated session owns the referenced event. As a result, any user holding EDIT or DELETE access can target any eventID in the database.
The weakness is classified as an Insecure Direct Object Reference under [CWE-639]. OpenCATS enforces role-based access level checks for the action category but omits per-record ownership validation. Private events, which are intended to remain restricted to their creator, are reachable through parameter tampering because the backend trusts the client-supplied identifier.
Root Cause
The root cause is a missing authorization check between the access-level gate and the database mutation. The onEditEvent() and onDeleteEvent() handlers resolve the submitted eventID without correlating the event's owner to $_SESSION['CATS'] user identity. The Calendar.php library methods that perform the UPDATE and DELETE queries likewise do not filter rows by owning user. This allows horizontal privilege escalation across calendar records.
Attack Vector
An attacker must first authenticate to the OpenCATS instance and hold at least EDIT or DELETE access on the contacts module. The attacker then submits a crafted request to the calendar edit or delete endpoint with an eventID corresponding to another user's event. The server executes the modification or deletion without ownership validation, altering or removing the targeted record.
// Patch excerpt from ajax/editActivity.php
// Adds the previously missing authorization check
die();
}
+if ($_SESSION['CATS']->getAccessLevel('contacts.editActivity') < ACCESS_LEVEL_EDIT)
+{
+ $interface->outputXMLErrorPage(-1, ERROR_NO_PERMISSION);
+ die();
+}
+
if (!$interface->isRequiredIDValid('activityID'))
{
$interface->outputXMLErrorPage(-1, 'Invalid activity ID.');
Source: OpenCATS Commit aa3b414
The companion patch in ajax/deleteActivity.php applies the same getAccessLevel('contacts.deleteActivity') gate before any mutation runs.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-113349
Indicators of Compromise
- Unexpected modification or disappearance of calendar entries reported by OpenCATS users
- Web server access logs showing repeated POST requests to the calendar module referencing non-sequential or enumerated eventID values
- Session activity where a single authenticated user mutates events across many different owner IDs in a short window
Detection Strategies
- Review OpenCATS application logs for onEditEvent and onDeleteEvent invocations and correlate the acting user against the stored event owner.
- Compare the installed OpenCATS version against release v0.10.0 using git log or the admin footer banner to identify unpatched deployments.
- Deploy web application firewall rules that flag high-volume eventID parameter changes from a single session.
Monitoring Recommendations
- Enable verbose PHP and web server access logging on the modules/calendar/ path and forward events to a central log platform.
- Alert on authenticated sessions issuing bulk calendar edit or delete requests outside normal recruiter workflows.
- Audit the OpenCATS user table for accounts holding ACCESS_LEVEL_EDIT or higher on contacts and verify they are still required.
How to Mitigate CVE-2026-113349
Immediate Actions Required
- Upgrade OpenCATS to version 0.10.0 or later, which introduces authorization checks in the affected AJAX endpoints and module actions.
- Reduce the number of accounts holding EDIT and DELETE access on the contacts module to the minimum operationally necessary.
- Back up the calendar and activity tables before upgrading so that tampered records can be restored if abuse is discovered.
Patch Information
The fix is delivered in OpenCATS release v0.10.0. The remediation is implemented in commit aa3b414c, which adds getAccessLevel() validation to the vulnerable AJAX endpoints and module actions. Additional context is available in the VulnCheck advisory and OpenCATS issue #720.
Workarounds
- Restrict network access to the OpenCATS instance to trusted internal networks or VPN users while the patch is applied.
- Temporarily lower user access levels on the contacts module to below ACCESS_LEVEL_EDIT for any account that does not require calendar mutation rights.
- Place a reverse proxy rule in front of modules/calendar/ that blocks requests whose eventID parameter does not match the authenticated session's events, until the upgrade is complete.
# Example upgrade procedure for a self-hosted OpenCATS deployment
cd /var/www/opencats
sudo -u www-data git fetch --tags
sudo -u www-data git checkout v0.10.0
sudo systemctl reload php-fpm nginx
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

