CVE-2026-100899 DevaslanPHP CVE debrief

Who should care

Defenders responsible for DevaslanPHP project-management deployments, particularly those using the Timesheet Dashboard, should assess their exposure to this vulnerability and prioritize verification and potential remediation.

Why it matters

This SQL injection vulnerability in DevaslanPHP project-management allows remote attackers to execute malicious SQL queries, potentially leading to data tampering or unauthorized access. Defenders should prioritize verifying the presence of this vulnerability in their deployments and assess the exposure of their Timesheet Dashboard.

• Remote SQL injection attacks are possible
• Verification of deployed versions and exposure is necessary
• Compensating controls or monitoring may be required

Technical summary

The SQL injection vulnerability exists in the Timesheet Dashboard of DevaslanPHP project-management versions 1.2.1 through 1.2.4 and v2.0.0-beta1. The flaw is located in the MonthlyReport.php file, where an attacker can manipulate the filter argument to execute SQL injection attacks remotely. This vulnerability allows remote attackers to execute malicious SQL queries, potentially leading to data tampering or unauthorized access. Defenders should prioritize verifying the presence of this vulnerability in their deployed versions of DevaslanPHP project-management and assess the exposure of their Timesheet Dashboard. The CVE record and NVD entry provide details about the SQL injection vulnerability in DevaslanPHP

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their deployed versions of DevaslanPHP project-management and assess the exposure of their Timesheet Dashboard.

Recommended defensive actions

• Verify the presence of this vulnerability in deployed versions of DevaslanPHP project-management
• Assess the exposure of the Timesheet Dashboard
• Consider compensating controls or monitoring for potential SQL injection attacks
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details about the SQL injection vulnerability in DevaslanPHP project-management. However, the vendor did not respond to the disclosure, and there is no information on affected or fixed versions.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.