Possible Progress WhatsUp Gold Path Traversal and UNC Coercion via core API (via webserver)

PremiumReviewedSigma · High · v1
Category
webserver
Author
HuntRule
Published
2026-09-07
Updated
2026-09-07

ATT&CK techniques

Initial Access → Cred Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects requests to the WhatsUp Gold AlarmCustomizer and WebContent core API endpoints that carry directory traversal sequences or UNC paths such as backslash-backslash host references and administrative shares. This pattern was used to read arbitrary files and coerce the server into authenticating to attacker SMB shares to capture NTLM credentials. Detecting it exposes file read and forced-authentication attacks against the monitoring server.

Related detections9 linkedT1190 — drag to rearrange
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Ivanti Pulse Connect Secure Auth Bypass via TOTP Backup Code Path Traversal (via webserver)
Possible Citrix Bleed Session Token Leak via OpenID Configuration Endpoint (CVE-2023-4966) (via webserver)
Suspicious Citrix StoreFront SAML Test Endpoint Access for XSS (CVE-2023-5914) (via webserver)
Possible Citrix ShareFile Unauthenticated Upload Path Traversal Webshell (CVE-2023-24489) (via webserver)
Possible Citrix NetScaler Gateway Buffer Overflow via formssso Endpoint (CVE-2023-3519) (via webserver)
Possible Progress WS_FTP Ad Hoc Deserialization via AHT_DEFAULT_UPLOAD_PARAMETER Marker
Possible Progress WhatsUp Gold Path Traversal and UNC Coercion via core API (via webserver)
Pivot detection · T1190 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.