Cyber Resilience

CVE-2026-31954

CSRF in Emlog ≤ 2.6.6

Public PoCCSRF
Published
11 March 2026
Modified
17 March 2026
Patch / advisory
CVSS Score v3.1 0.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N
EPSS Score 0.0015 4th percentile
Risk Priority 21 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-31954 is a uncategorised-severity CSRF (CWE-352) vulnerability in Emlog Emlog. Its CVSS base score is 0.0.

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SC-23 (Session Authenticity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-31954 affects Emlog, an open source website building system, in versions 2.6.6 and earlier. The vulnerability resides in the delete_async action, which implements asynchronous deletion but omits a call to LoginAuth::checkToken(), thereby enabling cross-site request forgery (CSRF) attacks as classified under CWE-352. Published on 2026-03-11, it carries a CVSS v3.1 base score of 0.0 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:N), indicating no direct impact on confidentiality, integrity, or availability.

An attacker can exploit this CSRF vulnerability by tricking an authenticated user with low privileges (PR:L) into visiting a malicious webpage that submits a forged request to the delete_async endpoint over the network (AV:N) with low attack complexity (AC:L) and no required user interaction beyond the initial visit (UI:N). Successful exploitation allows the attacker to perform unauthorized asynchronous deletions on behalf of the victim within the same scope (S:U), potentially removing blog posts, files, or other content managed by the Emlog instance.

The GitHub security advisory at https://github.com/emlog/emlog/security/advisories/GHSA-xc26-93qj-rcrw provides details on mitigation, including recommended patches or upgrades for affected Emlog installations.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Emlog is an open source website building system. In 2.6.6 and earlier, the delete_async action (asynchronous delete) lacks a call to LoginAuth::checkToken(), enabling CSRF attacks.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-31612Same product: Emlog Emlog
CVE-2024-41344Shared CWE-352
CVE-2025-30862Shared CWE-352
CVE-2024-39063Shared CWE-352
CVE-2023-23704Shared CWE-352
CVE-2024-39157Shared CWE-352
CVE-2024-54436Shared CWE-352
CVE-2025-25123Shared CWE-352
CVE-2023-28989Shared CWE-352
CVE-2023-46092Shared CWE-352

Affected Assets

emlog
emlog
≤ 2.6.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.3.2
  • V3.5.1
  • V10.2.1

Mitigating Controls (NIST 800-53 r5) AI

Access enforcement requires verifying that state-changing requests originate from the authenticated user rather than a forged cross-site source.

Protecting session authenticity prevents attackers from replaying or forging authenticated requests via the victim's browser.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require anti-CSRF controls such as tokens or SameSite attributes.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

mitigates

By denying access to phishing or malicious sites, the control lowers the likelihood that a user will be tricked into submitting a forged request that performs an unintended action on another site.

References