Live › vulnerability › CVE-2026-116512
The Project Manager WordPress plugin up to and including 4.1.1 passes the 'id' parameter into a validation string that is split and run as PHP functions. An unauthenticated attacker can make the server execute code.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 08:34 UTC. All times on this page are UTC.
Sites running the Project Manager WordPress plugin version 4.1.1 or earlier are exposed through the REST route that handles the 'id' parameter. The flaw is reached before the plugin's permission check, so no login is needed. Sites without this plugin, or with a newer version, are not affected by this report.
No product ranges from the sources yet.
wp plugin list4.1.1 or not present at all4.1.1 (no fixed version stated in the sources)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The Project Manager – AI Powered Project Management, Task Management, Kanban Board & Time Tracker plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 4.1.1 via the 'id' parameter parameter. This is due to unsanitized 'id' parameter value concatenated directly into the pipe-delimited validation rule string, which is then split and each token invoked as a dynamic PHP function with no allowlist check. This makes it possible for unauthenticated attackers to execute code on the server. This is exploitable by unauthenticated attackers because WordPress core executes the route argument's validate_callback inside WP_REST_Server::dispatch() before the route's permission_callback is invoked, meaning the Project_Manage_Capability authorization gate is never reached on the vulnerable code path.
This page as .md · .json · in your agent: get_signal("CVE-2026-116512")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.