CVE-2026-13549: Authorization Bypass in CodeAstro Complaint Management System 1.0
CodeAstro Complaint Management System version 1.0 contains an authorization bypass vulnerability in its Report deletion functionality. An attacker can remotely trigger improper access controls in the deletereport function, allowing unauthorized deletion or modification of report data. The vulnerability requires user interaction (such as tricking an administrator into clicking a malicious link) but does not require authentication. Public exploit code is available, increasing the risk of opportunistic attacks.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.4 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
- Weaknesses (CWE)
- CWE-285, CWE-639
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-06-29 / 2026-06-29
NVD description (verbatim)
A security flaw has been discovered in CodeAstro Complaint Management System 1.0. The affected element is the function deletereport of the file application/controllers/Report.php of the component Report Endpoint. The manipulation results in authorization bypass. The attack can be executed remotely. The exploit has been released to the public and may be used for attacks.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-13549 affects the deletereport function within application/controllers/Report.php of CodeAstro Complaint Management System 1.0. The flaw stems from inadequate authorization checks on the Report Endpoint, permitting an unauthenticated or insufficiently privileged user to delete or tamper with reports. The attack surface is the network (AV:N), requires low complexity (AC:L), no privilege escalation (PR:N), but does require some user interaction (UI:R). The impact is limited to integrity and availability of report data, with no confidentiality impact. This aligns with CWE-285 (Improper Authorization) and CWE-639 (Authorization Bypass Through User-Controlled Key), both common patterns in access control failures.
Business impact
Organizations relying on CodeAstro's complaint management system face data loss and audit trail tampering. Critical complaint records—potentially including customer grievances, regulatory submissions, or internal escalations—can be deleted without proper authorization. This undermines data integrity, creates compliance violations (especially under frameworks requiring immutable audit logs), and damages stakeholder trust. If attackers exploit this to erase complaints, evidence of systemic issues may be lost, hampering root-cause analysis and regulatory investigations.
Affected systems
CodeAstro Complaint Management System version 1.0 is the sole affected product. Organizations running this version should inventory all instances, including development, staging, and production environments. Earlier or later versions have not been explicitly identified as affected; however, security assessments should confirm version lineage and patch status across the entire deployment footprint.
Exploitability
Exploitability is moderate-to-high. Public exploit code is available, significantly lowering the barrier to attack. An attacker must trick a user (typically an administrator or privileged user) into following a malicious link or performing an action that triggers the vulnerable endpoint. Network accessibility is unrestricted, and no special configuration or privileges are needed to initiate the attack. The presence of public exploits and the straightforward nature of authorization bypass attacks mean defenders should assume active exploitation is plausible.
Remediation
The primary remediation is to upgrade CodeAstro Complaint Management System to a patched version. Organizations should consult the vendor's security advisory to identify the minimum patched version. Pending patching, implement compensating controls: restrict network access to the Report Endpoint via firewall or WAF rules, enforce authentication at the application perimeter, disable or restrict the deletereport function if not critical to operations, and monitor deletion activities in logs. Consider implementing additional role-based access controls to enforce principle of least privilege on report operations.
Patch guidance
Contact CodeAstro or check their official security advisory for the available patch and version number. Apply patches promptly to production systems and verify functionality in a non-production environment first. Ensure all instances (including development, staging, and any legacy or disconnected systems) are patched uniformly. Test that legitimate report deletion workflows continue to function correctly after patching, and validate that unauthorized deletion attempts are now blocked.
Detection guidance
Monitor application logs for suspicious deletereport requests, particularly those from unexpected IP addresses or originating outside normal administrative workflows. Look for repeated failed authorization checks or patterns of report deletion by unauthorized users. WAF or IDS rules should flag POST/DELETE requests to the Report Endpoint lacking proper authentication headers or coming from untrusted sources. Check database transaction logs for unexpected deletions of complaint records, and correlate timestamps with user activity logs. Implement alerting on any deletereport calls from non-administrative accounts.
Why prioritize this
Although the CVSS score of 5.4 is MEDIUM, the combination of public exploit availability, network-accessible attack surface, and direct impact on data integrity elevates practical risk. Complaint management systems often store sensitive customer, employee, or regulatory data. The ability to delete records without authorization poses significant compliance and operational risk, particularly for organizations subject to data retention or audit trail requirements. Patch this vulnerability within 30 days of release or immediately if you cannot restrict network access.
Risk score, explained
The CVSS 3.1 score of 5.4 (MEDIUM) reflects the attack complexity and the lack of confidentiality impact. However, the score does not fully capture the practical risk introduced by publicly available exploits and the sensitivity of complaint data. Organizations managing sensitive complaints or operating in regulated industries should weight this vulnerability higher in their prioritization matrix. The presence of exploit code and the user-interaction requirement (which is often achievable via phishing or social engineering) justify immediate attention despite the MEDIUM severity rating.
Frequently asked questions
Does this affect CodeAstro versions other than 1.0?
The vulnerability is confirmed in version 1.0. Consult CodeAstro's advisory to determine if other versions are affected. Do not assume earlier or later versions are safe without explicit vendor confirmation.
Can an attacker delete reports without any user interaction?
No. The vulnerability requires user interaction (UI:R in the CVSS vector), meaning the attacker must trick a user into triggering the malicious request. This is often achieved via phishing, malicious links, or social engineering, but it is not fully automated exploitation.
What should I do if I cannot patch immediately?
Implement network segmentation to restrict access to the Report Endpoint to known administrative IPs, enforce multi-factor authentication on admin accounts, disable the deletereport function if not actively used, and implement detailed logging and alerting on any deletion attempts. These controls reduce risk while you prepare for patching.
Is this listed in the CISA Known Exploited Vulnerabilities catalog?
No, this vulnerability is not currently listed on CISA's KEV catalog. However, public exploit code exists, so it should be treated with the same urgency as KEV-listed flaws. Monitor for updates to CISA's catalog and industry advisories.
This analysis is provided for informational purposes and based on publicly available vulnerability data as of the publication date. CVSS scores, patch versions, and vendor guidance are subject to change; verify all technical details against the official CodeAstro security advisory before taking action. SEC.co makes no warranty regarding the completeness or accuracy of this analysis. Organizations are responsible for independently assessing their exposure and implementing appropriate security controls. This document does not constitute legal, compliance, or professional security advice. Source: NVD (public-domain), retrieved 2026-08-08. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10154MEDIUMDolibarr ERP CRM Authorization Bypass in Messaging Module
- CVE-2026-10212MEDIUMAstrBot 4.24.2 Authorization Bypass via Session ID Manipulation
- CVE-2026-11461MEDIUMhermes-agent Authorization Bypass in Resume Endpoint
- CVE-2026-11500MEDIUMWeaviate Authorization Bypass in Static API Key Handler
- CVE-2026-13512MEDIUMDatabend Authorization Bypass in Session Manager
- CVE-2026-13534MEDIUMAuthorization Bypass in CherryHQ cherry-studio Memory Service
- CVE-2026-14608MEDIUMSourceCodester CET Grading System Authorization Bypass
- CVE-2026-14793MEDIUMCraft CMS Authorization Bypass in Global Sets Reordering