Skip to main content

BugTracker.NET EUVDEUVD-2026-94284

| CVE-2026-92532 HIGH
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-10-07 INCIBE GHSA-h4mm-35cr-vc9q
7.5
CVSS 4.0 · Vendor: INCIBE
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as application administrator
  2. Delivery
    Reconfigure attachment path to web-accessible directory
  3. Exploit
    Upload malicious .aspx via attachment feature
  4. Execution
    Request uploaded file URL to trigger execution
  5. Impact
    Run arbitrary code as web service account

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires an authenticated BugTracker.NET administrator (PR:H) who first modifies the application configuration so that uploaded attachments are stored in a directory served by the web server - a non-default change. The attacker then abuses the attachment feature's missing file-extension validation to upload an executable .aspx file and requests its URL to trigger server-side execution as the web service account. Limiting factors: administrator-level access is mandatory, the web-accessible attachment storage configuration is not the default (reflected as AT:P in the CVSS 4.0 vector), and the server must process .aspx (ASP.NET/IIS); no victim user interaction is required (UI:N).

Impact

This is a genuine but conditional remote code execution flaw (CWE-434 unrestricted file upload) that the signals consistently describe as LOW real-world priority despite the HIGH CVSS 4.0 base score of 7.5. The vendor CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H) confirms three strong limiting factors: PR:H means the attacker must already hold administrator privileges, and AT:P indicates a precondition outside the attacker's control (the admin must first reconfigure the application to store attachments in a web-accessible directory). In other words, an attacker who can trigger this already controls the application's administrative plane, sharply reducing the marginal risk. There is NO EPSS score, NO CISA KEV listing, and NO public exploit referenced in the provided data, so exploitation is 'no public exploit identified at time of analysis.' The subsequent-system impact is explicitly N (SC:N/SI:N/SA:N), meaning impact is contained to the host web service account rather than cascading. Net assessment: a legitimate post-authentication RCE worth patching, but not an emergency - the high score is driven by full CIA impact, while the practical likelihood is throttled by the admin-privilege and non-default-configuration requirements. Missing data to flag: no EPSS, no KEV, no POC, and no vendor-confirmed fixed version in the provided references.

Exploit ScenarioDerived

An attacker who has obtained (or abused) BugTracker.NET administrator credentials reconfigures the attachment storage path to point to a web-accessible directory, then uploads a malicious .aspx file through the attachment feature, which lacks file-extension validation. The attacker then browses to the uploaded file's URL, causing the web server to execute it and granting arbitrary code execution under the web service account. No public proof-of-concept is referenced, and the attack requires high privileges plus a non-default configuration change, so it is a post-authentication scenario rather than a drive-by.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 07, 2026

Authenticated attackers holding BugTracker.NET administrator privileges can achieve server-side code execution by first reconfiguring the application so that attachments are stored in a web-accessible directory, then uploading an .aspx file that the attachment feature fails to filter by extension. Because the uploaded file lands in a location the web server serves and ASP.NET/IIS will process executable handlers there, requesting its URL runs arbitrary code under the web service account. Exploitation is heavily gated: it requires PR:H administrator access and a non-default storage configuration (reflected as AT:P in the CVSS 4.0 vector), and no public exploit code has been identified at time of analysis; the signals consistently describe this as a low real-world priority issue despite a high CVSS 4.0 base score of 7.5.

RemediationAI

No vendor-released patch was identified at time of analysis, so remediation is configuration- and deployment-hardening based, tracked against the INCIBE advisory (https://www.incibe.es/en/incibe-cert/notices/aviso/multiple-vulnerabilities-bugtrackernet). The most effective control is to move attachment storage out of the web root entirely - restore the non-default, non-web-accessible storage path - which removes the HTTP execution path completely; the trade-off is that any existing links to attachment URLs in tickets or notifications will break. Where attachments must remain web-served, strip executable handler mappings for that directory in IIS (remove the .aspx/.ashx/.asmx handlers or set them to Deny for the upload folder) so that any dropped file is served as inert content, accepting that the mapping must be re-applied whenever the site is rebuilt or migrated. Add a server-side upload extension allowlist limited to safe document and image types, rejecting double extensions and verifying content type, at the cost of some legitimate attachment types being refused. As supporting controls, restrict administrator accounts to a minimal trusted set, audit configuration changes that alter storage paths, and run the application pool under a low-privilege identity with no write access outside its own directories to limit post-exploitation reach. Until a fix ships, treat any deployment with web-accessible attachment storage as exposed and prioritize it for the configuration review above.

Affected VersionsENISA

BugTracker.NET all versions

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 root cause is CWE-434 (Unrestricted Upload of File with Dangerous Type) in BugTracker.NET's attachment subsystem, an ASP.NET web application typically hosted on IIS. The flaw is situational rather than a pure remote upload bug: the administrator-only application configuration has historically allowed operators to point attachment storage at an arbitrary directory, and if that directory sits under the site root, files become directly requestable over HTTP. With no allowlist or extension denylist applied to uploaded attachment names, an attacker can place an .aspx file that IIS maps to the ASP.NET handler, giving server-side execution in the context of the application pool identity. The CPE cpe:2.3:a:bugtracker.net:bugtracker.net:*:*:*:*:*:*:*:* carries wildcard versioning, indicating the advisory does not scope an exact release range, so all deployments exposing both the configuration option and the attachment feature should be treated as potentially affected. The two independent scoring perspectives agree on impact (high confidentiality, integrity and availability) but differ in difficulty: CVSS 4.0 marks the attack as AT:P because the web-served storage layout is not the default, while the 3.1 assessment encodes the same limitation as AC:H.

Know when Bugtracker Net gets its next vulnerability

  • 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

Vendor (INCIBE) PRIMARY 7.5 HIGH
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.6 MEDIUM

Admin privileges give PR:H and the required non-default web-accessible storage configuration maps to AC:H in 3.1; code runs on the same host so S:U with full C/I/A:H.

3.1 AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (INCIBE).

CVSS VectorVendor: INCIBE

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
Present
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

Unrestricted file upload vulnerability in the BugTracker.NET attachment functionality. An authenticated user with administrator privileges could modify the application configuration to store files in a directory accessible via the web interface. Due to the lack of proper file extension validation, an attacker could upload a malicious ASPX file and subsequently execute it on the server. A successful exploit could allow arbitrary code execution with the privileges of the account used by the web service.

Executive ViewAI

Why It Matters

A high-severity flaw in BugTracker.NET allows an attacker who already holds application administrator rights to upload a crafted attachment that the web server then executes, potentially giving that person control of the server hosting the tool. Exploitation is gated by two conditions - administrator credentials and a non-default attachment storage configuration - so real-world exposure is limited to environments with loose administrative access or customized deployments. Leadership should treat this as an access-governance and configuration-hygiene issue rather than an imminent external threat, while confirming that no attachment directories are currently web-exposed.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: store attachments outside the IIS web root so uploaded files are never served or executed; strip execute and ASP.NET handler permissions from any attachment directory; enforce strict upload extension allow-listing and add IIS request filtering rules blocking executable extensions (.aspx, .ashx, .asmx, .asp, .config); restrict and audit BugTracker.NET administrator accounts (PR:H) with least privilege and MFA at the identity layer; monitor for new files or configuration changes in attachment paths; and apply virtual patching at the WAF/reverse proxy to block requests for uploaded files under attachment directories.

Threat Intelligence Overview

EPSS Score
0.3%
Top 79% exploitable
Prevalence
Low
niche open-source ASP.NET bug tracker, limited enterprise footprint
Data Quality
3 sources
Confidence: Low

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Medium
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy