CVE-2026-42286Disclosure

LOWCVSS 8.4 · HIGH

Signal is active with 2 mentions in latest observed window

Immediate actions

  • Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD description

Emlog is an open source website building system. Prior to version 2.6.11, missing CSRF protection in critical admin functions allows attackers to trick authenticated administrators into performing unauthorized actions like system registration, plugin management, and configuration changes. This issue has been patched in version 2.6.11.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-352

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

  • Patch or workaround signal is available
  • 2 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 2 signals
  • Technical details provided in 2 signals
  • Disclosure: 2 classified signals
  • 2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d
01122Mentions · 2026-05-09: 2Patch / Workaround · 2026-05-09: 2Technical Details · 2026-05-09: 205-09
Signal classification1 categories
Disclosure
2100.0%
Referenced assets2 URLs
Full discourse2 posts
  • CVE@CVEnew
    Disclosure

    CVE-2026-42286 Emlog is an open source website building system. Prior to version 2.6.11, missing CSRF protection in critical admin functions allows attackers to trick authenticated … https://www.cve.org/CVERecord?id=CVE-2026-42286

    Post summary

    The text reports that Emlog’s pre‑2.6.11 versions suffer from a CSRF flaw in admin functions, noting that the issue is resolved in version 2.6.11.

    0000097
    57.5K followersView on X
  • Vulmon Vulnerability Feed@VulmonFeeds
    Disclosure

    CVE-2026-42286 Cross-Site Request Forgery in Emlog Prior to Version 2.6.11 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-42286

    Post summary

    This brief disclosure identifies a CSRF flaw in Emlog that is present in versions before 2.6.11, indicating that updating to 2.6.11 resolves the issue, with no exploitation or PoC details provided.

    0000039
    4.0K followersView on X

Explore more