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-112783 Overview
OpenCATS versions prior to 0.10.0 contain a missing authorization vulnerability [CWE-862] in two AJAX endpoints: ajax/deleteActivity.php and ajax/editActivity.php. The endpoints fail to verify whether the authenticated user holds edit privileges before processing activity modification or deletion requests. READ-level users can supply an arbitrary activityID via GET or POST and alter or remove activity and pipeline history for candidates, contacts, and companies. The flaw affects data integrity across the recruiting workflow and can erase records of past interactions, interview notes, and candidate pipeline movements. Exploitation requires only a valid low-privilege account on the OpenCATS instance.
Critical Impact
Any authenticated READ-level user can tamper with or destroy activity history for every candidate, contact, and company stored in OpenCATS.
Affected Products
- OpenCATS versions prior to 0.10.0
- ajax/deleteActivity.php endpoint
- ajax/editActivity.php endpoint
Discovery Timeline
- 2026-10-20 - CVE-2026-112783 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-112783
Vulnerability Analysis
OpenCATS is an open-source applicant tracking system that assigns users one of several access levels, including READ, EDIT, and higher administrative tiers. The two vulnerable AJAX scripts validate that a user is authenticated and that an activityID is well-formed, but they omit the access-level check that normally guards write operations. As a result, the server executes the delete or edit action on behalf of any logged-in user. An attacker with a READ account can enumerate activity IDs and silently rewrite or purge the recruiting pipeline history. The impact is bounded to integrity: confidentiality and availability of the broader application are not directly compromised, which aligns with the limited-integrity-only CVSS vector published for this issue. See the VulnCheck Security Advisory for OpenCATS for additional context.
Root Cause
The root cause is an absent authorization check in the request handlers. Prior to the patch, neither script invoked getAccessLevel('contacts.editActivity') or getAccessLevel('contacts.deleteActivity') before performing the state change. The code trusted session authentication alone and skipped role-based authorization, satisfying the pattern described in [CWE-862: Missing Authorization].
Attack Vector
Exploitation is network-based and requires an authenticated session at the lowest privilege tier. An attacker submits an HTTP GET or POST request to ajax/deleteActivity.php or ajax/editActivity.php with an attacker-chosen activityID parameter. The server returns success and persists the modification without verifying the caller's role. No user interaction, special timing, or custom tooling is required beyond a browser or curl.
die();
}
+if ($_SESSION['CATS']->getAccessLevel('contacts.deleteActivity') < 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 patch inserts the same ACCESS_LEVEL_EDIT guard in both deleteActivity.php and editActivity.php, rejecting callers that do not meet the required access level.
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-112783
Indicators of Compromise
- HTTP requests to /ajax/deleteActivity.php or /ajax/editActivity.php originating from user sessions whose database role is READ-only.
- Unexpected deletions or modifications in the OpenCATS activity table where the acting user lacks edit permissions in the application role mapping.
- Spikes in XML responses from the two endpoints that do not match normal recruiter workflow volume.
Detection Strategies
- Enable verbose web server access logging and alert on POST or GET requests to the two AJAX endpoints that are followed by database write operations.
- Correlate the authenticated session's access level with the endpoint invoked; flag any invocation by a user below ACCESS_LEVEL_EDIT.
- Review audit logs for activity records whose last_modified or deletion timestamps cluster around requests from a single low-privilege account.
Monitoring Recommendations
- Forward OpenCATS web server and application logs to a centralized logging platform for long-term retention and query.
- Build dashboards that break down activity edit and delete volume by user role to surface anomalies.
- Alert on repeated 200-OK responses from deleteActivity.php tied to session cookies belonging to accounts that should not have write access.
How to Mitigate CVE-2026-112783
Immediate Actions Required
- Upgrade OpenCATS to version 0.10.0 or later, which includes the authorization checks in both AJAX endpoints.
- Audit all existing user accounts and reduce privilege levels where READ access is not strictly required.
- Review the activity table for unauthorized modifications or deletions since the vulnerable version was deployed.
Patch Information
The fix is contained in OpenCATS Release v0.10.0 and tracked in OpenCATS Issue #720 Discussion. The relevant code change is published in OpenCATS commit aa3b414, which adds getAccessLevel checks to both the Delete Activity Script and the Edit Activity Script.
Workarounds
- Restrict network access to the OpenCATS application so that only trusted recruiters can reach the AJAX endpoints.
- Backport the upstream patch by adding the ACCESS_LEVEL_EDIT check to ajax/deleteActivity.php and ajax/editActivity.php if an immediate upgrade is not possible.
- Temporarily disable or block the two endpoints at the reverse proxy or web server layer until the patched release can be deployed.
# Example nginx rule to block the vulnerable endpoints until patching
location ~ ^/ajax/(deleteActivity|editActivity)\.php$ {
deny all;
return 403;
}
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

