CVE-2024-48042Disclosure

LOWCVSS 9.1 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

Deserialization of Untrusted Data vulnerability in supsystic Contact Form by Supsystic contact-form-by-supsystic allows Command Injection.This issue affects Contact Form by Supsystic: from n/a through <= 1.7.28.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-82

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-04-02: 1Technical Details · 2026-04-02: 104-02
Signal classification1 categories
Disclosure
1100.0%
Full discourse1 post
  • BreakGlass Intelligence@BreakGlassIntel
    Disclosure

    Quick run -> German's opendir → X5S SECURE COMMAND platform: Server went dark before we could dump it. But pivoting from that one dead IP we mapped: - X5S[.]US: Offensive security platform with XSS management, WordPress scanning, backup file discovery - CVE-2024-48042 (CVSS 9.1): WordPress Contact Form RCE. -The "CVE-2026-4257" from the tweet doesn't exist? it was an internal lab designation? - Multi-cloud: Cloudflare (3 separate accounts), Shinjiru Malaysia, OVH Canada, Tencent Cloud - Operator: "Crili Aprl", cirliaa@proton[.]me, UK WHOIS + US phone + Chinese platform = obfuscation deep dive pending 😎

    Post summary

    The post discloses CVE-2024-48042 as a high‑severity WordPress Contact Form RCE, while also debunking a purported CVE-2026-4257 as nonexistent.

    00000627
    559 followersView on X

Explore more