CVE-2026-2351
Arbitrary File Read in WordPress Task Manager Plugin Allows Data Exposure
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| task_manager | task_manager_plugin | to 3.0.2 (inc) |
| eoxia | task_manager | to 3.0.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-73 | The product allows user input to control or influence paths or file names that are used in filesystem operations. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The Task Manager plugin for WordPress, in all versions up to and including 3.0.2, has a vulnerability in the callback_get_text_from_url() function that allows authenticated users with Subscriber-level access or higher to read arbitrary files on the server.
This means that an attacker who is logged in with minimal privileges can exploit this flaw to access the contents of any file on the server, potentially exposing sensitive information.
How can this vulnerability impact me? :
This vulnerability can have a significant impact because it allows attackers with low-level access to read sensitive files on the server.
- Exposure of sensitive information stored in server files.
- Potential leakage of configuration files, credentials, or other private data.
- Increased risk of further attacks leveraging the exposed information.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'The vulnerability exists in the Task Manager WordPress plugin versions up to 3.0.2, specifically in the AJAX callback function callback_get_text_from_url(). It allows authenticated users with Subscriber-level access or higher to read arbitrary files on the server.'}, {'type': 'paragraph', 'content': 'To detect exploitation attempts or the presence of this vulnerability on your system, you can monitor for AJAX requests to the endpoint that triggers the callback_get_text_from_url() function. These requests typically include POST data with a URL parameter that the plugin attempts to fetch.'}, {'type': 'paragraph', 'content': 'Suggested commands to detect such activity include:'}, {'type': 'list_item', 'content': 'Check web server access logs for POST requests to admin-ajax.php with the action parameter set to wp_ajax_get_text_from_url_tm.'}, {'type': 'list_item', 'content': "Example grep command on Apache or Nginx logs: grep 'POST.*admin-ajax.php' /var/log/apache2/access.log | grep 'action=wp_ajax_get_text_from_url_tm'"}, {'type': 'list_item', 'content': 'Use network monitoring tools to filter HTTP POST requests containing the action wp_ajax_get_text_from_url_tm.'}, {'type': 'list_item', 'content': 'Within WordPress, review user activity logs for Subscriber-level users making AJAX requests to this action.'}, {'type': 'paragraph', 'content': 'Since the plugin uses AJAX with nonce verification, attempts without valid nonces may fail, but monitoring for repeated or suspicious requests to this endpoint can help detect exploitation attempts.'}] [2, 4]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps for this vulnerability include:
- Update the Task Manager plugin to a version later than 3.0.2 once a patched release is available.
- If an update is not yet available, disable or remove the Task Manager plugin to prevent exploitation.
- Restrict access to the WordPress admin-ajax.php endpoint or specifically block AJAX requests with the action wp_ajax_get_text_from_url_tm for users with Subscriber-level access or lower.
- Review and tighten user permissions to ensure that only trusted users have Subscriber-level or higher access.
- Monitor server logs for suspicious AJAX requests targeting the vulnerable function and investigate any anomalies.
Since the vulnerability allows arbitrary file read via an authenticated AJAX callback, controlling access and disabling the vulnerable plugin are the most effective immediate mitigations.