Is there a public PoC exploit available for CVE-2026-19345?

Yes, a public proof-of-concept exploit is available for CVE-2026-19345. Prioritise patching immediately. EPSS: 0.5%.

Task Management System CVE-2026-19345

Q: What is the CVSS score of CVE-2026-19345?

CVE-2026-19345 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.5%.

EUVD-2026-54914 MEDIUM

Missing Authorization (CWE-862)

2026-08-09 VulDB

GHSA-v3hx-vw4q-qf5q

PHP Authentication Bypass Task Management System Code Projects

5.5

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.5 MEDIUM

Network-reachable PHP endpoint, no authentication required (PR:N), no interaction needed; impact limited to task record integrity and minor availability with no scope change.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Aug 09, 2026 - 10:22 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

Analysis Generated

Aug 09, 2026 - 10:00 vuln.today

CVE Published

Aug 09, 2026 - 09:30 cve.org

MEDIUM 6.9

DescriptionCVE.org

A vulnerability was found in code-projects Task Management System 1.0. This affects an unknown part of the file /user/UpdateTaskStatus.php. The manipulation of the argument task_id/val results in missing authorization. It is possible to launch the attack remotely. The exploit has been made public and could be used.

AnalysisAI

Missing authorization in code-projects Task Management System 1.0 allows remote unauthenticated attackers to manipulate task records by sending crafted requests to /user/UpdateTaskStatus.php with arbitrary task_id and val parameters. The server performs no permission check before processing the status update, enabling any network-reachable party to alter task data belonging to any user. A public proof-of-concept exploit exists per VulDB and a GitHub issue report, making opportunistic abuse straightforward despite the absence of a CISA KEV listing.

Technical ContextAI

The affected software is a PHP-based task management application identified by CPE cpe:2.3:a:code-projects:task_management_system:*:*:*:*:*:*:*:*, distributed by code-projects.org as an educational or demo project. The root cause is CWE-862 (Missing Authorization): the script /user/UpdateTaskStatus.php accepts HTTP parameters task_id and val and directly acts on them without verifying that the requesting party is authenticated or authorized to modify the referenced task. This is a server-side access control failure - the application trusts client-supplied identifiers with no session or ownership validation, a pattern common in rapidly-built PHP applications that separate authentication (login) from authorization (per-resource permission checks).

RemediationAI

No vendor-released patch has been identified at time of analysis. As an immediate compensating control, restrict unauthenticated access to /user/UpdateTaskStatus.php at the web server or WAF layer - for Apache, an auth_request or Require valid-user directive can gate the endpoint; for nginx, an auth_request module check achieves the same. The trade-off is that this shifts the auth burden to the web server rather than fixing the application logic, and misconfiguration could bypass the control. The correct long-term fix is to add a server-side session ownership check inside UpdateTaskStatus.php, verifying that the authenticated user's session matches the owner of the supplied task_id before processing the update. Given that code-projects software is designed as educational scaffolding, deploying it in production without such hardening is inadvisable. VulDB details and PoC context are available at https://vuldb.com/vuln/387181 and https://github.com/littleRain1355/PHPissue/issues/4.