CVE-2026-10284
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw has been found in DevaslanPHP project-management up to 2.0.0-beta1. Affected by this vulnerability is the function editComment/doDeleteComment of the file app/Filament/Resources/TicketResource/Pages/ViewTicket.php of the component Livewire Handler. Executing a manipulation can lead to improper authorization. The attack can be executed remotely. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe vulnerability exists in the Livewire handler functions editComment and doDeleteComment within the ViewTicket.php page of DevaslanPHP project-management application up to version 2.0.0-beta1. The functions lack proper authorization checks, allowing authenticated users to potentially edit or delete comments they should not have permission to modify.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the ViewTicket.php fileSearch the DevaslanPHP installation directory for files named 'ViewTicket.php', typically found in app/Livewire or app/Http/Livewire directoriesAffected if Unable to locate the file means the installation may be using a different structure or version
-
Examine editComment function authorizationOpen ViewTicket.php and locate the editComment method. Inspect whether it verifies that the current user owns the comment or has appropriate permissions before allowing modificationsAffected if The function lacks ownership/permission verification (e.g., no check like 'if (auth()->user()->id === $comment->user_id)' or equivalent permission check)
-
Examine doDeleteComment function authorizationOpen ViewTicket.php and locate the doDeleteComment method. Inspect whether it verifies that the current user owns the comment or has appropriate permissions before allowing deletionAffected if The function lacks ownership/permission verification (e.g., no check verifying the user is the comment owner or has admin rights)
-
Verify authorization is not handled at route or middleware level aloneConfirm the vulnerability exists at the function level - check that the Livewire component itself does not implement authorization, as middleware-level checks alone may not cover comment-specific ownershipAffected if No user-specific comment ownership validation exists within either function, even if general authentication middleware is present
If either editComment or doDeleteComment functions in ViewTicket.php lack proper user ownership or permission verification before allowing comment modifications, the environment is affected by this improper authorization vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authorization checks in both editComment and doDeleteComment functions to verify that the authenticated user has the appropriate permissions to modify the specific comment before allowing the operation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10284 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10284 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data