DevaslanPHP project-management up to 2.0.0-beta1 Livewire ViewTicket.php editComment/doDeleteComment improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in DevaslanPHP project-management up to 2.0.0-beta1. It has been rated as critical. Affected by this issue is the function editComment/doDeleteComment of the file app/Filament/Resources/TicketResource/Pages/ViewTicket.php of the component Livewire Handler. The manipulation leads to improper authorization.
This vulnerability is uniquely identified as CVE-2026-10284. The attack is possible to be carried out remotely. No exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in DevaslanPHP project-management up to 2.0.0-beta1. It has been rated as critical. This issue affects the function editComment/doDeleteComment of the file app/Filament/Resources/TicketResource/Pages/ViewTicket.php of the component Livewire Handler. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity, and availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-10284. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/31/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
The project was informed of the problem early through an issue report but has not responded yet. By approaching the search of inurl:app/Filament/Resources/TicketResource/Pages/ViewTicket.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
05/31/2026 Advisory disclosed05/31/2026 VulDB entry created
05/31/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 140
Status: Not defined
CVE: CVE-2026-10284 (🔒)
GCVE (CVE): GCVE-0-2026-10284
GCVE (VulDB): GCVE-100-367577
Entry
Created: 05/31/2026 18:35Changes: 05/31/2026 18:35 (56)
Complete: 🔍
Submitter: Mitchell45
Cache ID: 216::103
Submit
Accepted
- Submit #825473: devaslanphp project-management < 2.0.0-beta1 Improper Authorization (by Mitchell45)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.