Webserver POST requests to Confluence setup/restore endpoints matching CVE-2023-22518 exploit traffic

Detects POST traffic to Confluence CVE-2023-22518 vulnerable endpoints based on URI patterns and HTTP status codes.

FreeReviewedSigma · Medium · v5
Category
webserver
Author
Andreas Braathen (mnemonic.io) (SigmaHQ), DRL 1.1
Published
2023-11-14
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies webserver requests using HTTP POST to specific Confluence endpoints associated with the CVE-2023-22518 exploit path. The observed behavior matters because successful exploitation can allow unauthorized administrative account creation and command execution attempts. Detection relies on webserver HTTP telemetry, matching request method, targeted URI query substrings, and acceptable HTTP response status codes.

Related detections9 linkedT1190 — drag to rearrange
Cleo Autorun Exploitation via Healthcheck File Drop
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
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)
Webserver POST requests to Confluence setup/restore endpoints matching CVE-2023-22518 exploit traffic
Pivot detection · T1190 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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