EUVD-2026-91700
GHSA-rprh-3hxw-c233
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to TaskingAI instance
-
DeliveryInvoke QR Code Generator plugin
-
ExploitSupply traversal payload in project_id
-
Executionsave_base64_image writes outside target dir
-
ImpactOverwrite/plant arbitrary files on server
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the QR Code Generator plugin to be present/enabled in a TaskingAI v0.3.0 deployment and an attacker with a valid low-privileged authenticated session (CVSS PR:L), who then supplies a malicious project_id parameter to reach the vulnerable save_base64_image function. Limiting factors: authentication is required (not anonymous), the specific plugin must be in use, and SSVC marks the attack non-automatable, so exploitation is per-instance and interactive rather than mass-scannable; impact is bounded to writing image-format file content, which constrains but does not eliminate downstream code-execution or file-overwrite potential. |
| Impact | Signals are moderately consistent and point to a real-but-not-urgent issue. The provided CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N) describes a network-reachable, low-complexity attack requiring only low privileges, scoring 8.1 (High) with I:H/A:H and no confidentiality impact. SSVC frames it as Exploitation=poc, Automatable=no, Technical Impact=partial - the 'no' on automatability tempers the network vector, since each attack needs an authenticated session against a specific instance rather than mass scanning. A public proof-of-concept exists (a gist and the vendor GitHub issue), so exploit code is available, but this is NOT the same as active exploitation: there is no CISA KEV listing and no EPSS score was provided, so widespread or automated exploitation cannot be inferred. Net assessment: this is a legitimate arbitrary-file-write flaw with working POC code, but its real-world priority is constrained by the authentication requirement (PR:L), the non-automatable nature, and the low deployment footprint of TaskingAI. It should be patched by TaskingAI operators but does not rise to emergency 'exploited-in-the-wild' status on current evidence. |
| Exploit ScenarioDerived | An attacker who already holds low-privileged authenticated access to a TaskingAI v0.3.0 instance invokes the QR Code Generator plugin and supplies a crafted project_id containing path-traversal sequences, causing save_base64_image to write an attacker-controlled image file outside the intended directory. By targeting a sensitive location they can overwrite existing files or plant content on the server filesystem. A public proof-of-concept is available (gist and the TaskingAI GitHub issue), lowering the barrier to reproduction. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 02, 2026
Path traversal in the TaskingAI QR Code Generator plugin v0.3.0 allows an authenticated, low-privileged attacker to write image files to arbitrary locations on the server filesystem by manipulating the project_id parameter, affecting deployments where the plugin is enabled. Publicly available exploit code exists, and CISA's SSVC framework classifies the attack as non-automatable. Impact is primarily integrity (file overwrite) and availability (disk consumption or service disruption), with a CVSS of 8.1; the write is constrained to image-format content but may enable further compromise if sensitive paths are writable.
RemediationAI
No vendor-released patch identified at time of analysis. As an immediate compensating control, disable or remove the QR Code Generator plugin if it is not essential, accepting the loss of QR code generation functionality. If the plugin must remain active, restrict access to authenticated users with the lowest necessary privileges and deploy input validation to reject project_id values containing path traversal sequences (e.g., '../', '..\', absolute paths) - this can be implemented via a reverse proxy/WAF rule or a code patch to the save_base64_image function. Run the TaskingAI service with filesystem permissions limited to its intended data directories to reduce overwrite impact, and monitor for unexpected file writes. Refer to the GitHub issue (https://github.com/TaskingAI/TaskingAI/issues/374), the public gist (https://gist.github.com/Ro1ME/357950ddd2f65566b1b33525651b5635), and the NVD entry (https://nvd.nist.gov/vuln/detail/CVE-2026-51907) for updates. Note that the SSVC decision 'Exploitation: poc' and 'Automatable: no' suggests exploitation is interactive and per-instance, but the public proof-of-concept raises risk for exposed instances.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is a classic path traversal (CWE-22) in the save_base64_image function of TaskingAI's QR Code Generator plugin. This function accepts base64-encoded image data and a project_id parameter, then decodes and writes the image to a file path constructed using the unsanitized project_id. By injecting directory traversal sequences (e.g., '../'), an attacker can escape the intended storage directory and write files anywhere the TaskingAI process has write permissions. The function's limitation to image content constrains the payload to image formats, but overwriting existing images or writing images into web-accessible or configuration directories could lead to defacement, denial of service, or in some deployment configurations, code execution. Exploitation requires a valid low-privileged authenticated session (CVSS PR:L) and the QR Code Generator plugin to be present and enabled. The provided CPE (cpe:2.3:a:n/a:n/a) lacks vendor and product specificity, and EUVD does not list explicit affected version ranges beyond TaskingAI v0.3.0.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Network-facing plugin reachable by an authenticated low-privileged user (PR:L, AV:N, AC:L); arbitrary file write yields high integrity and availability impact but no direct confidentiality disclosure (C:N).
Primary rating from Vendor (mitre).
CVSS VectorVendor: mitre
Lifecycle Timeline
2DescriptionCVE.org
In TaskingAI v0.3.0 in the QR Code Generator plugin save_base64_image function, a path traversal vulnerability allows attackers to write image files to arbitrary locations on the server filesystem by manipulating the project_id parameter.
Executive ViewAI
The TaskingAI QR Code Generator plugin v0.3.0 contains a path traversal flaw that lets an attacker with access to the plugin write image files to arbitrary server locations, undermining file integrity and potentially consuming disk space or disrupting service on affected deployments. No vendor-released patch identified at time of analysis, and publicly available exploit code exists, so organizations running this plugin face elevated risk. Leadership should prioritize identifying and isolating any deployments where the plugin is enabled, as the flaw is non-automatable but can be exploited to overwrite files or enable further compromise if sensitive paths are writable.
No vendor-released patch identified at time of analysis. Interim mitigations: disable or remove the TaskingAI QR Code Generator plugin v0.3.0 if not required; restrict filesystem write permissions for the TaskingAI service account; block path traversal patterns at the WAF or reverse proxy; monitor for unexpected image files, file overwrites, and disk consumption; isolate affected deployments from sensitive data and networks.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Exploit-DB