Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker identifies victim's cti-transmute instance and their own user_id
-
DeliveryCraft malicious page with auto-firing GET/fetch requests to target endpoints
-
ExploitLure authenticated analyst to malicious page via phishing
-
ExecutionBrowser sends session-authenticated request to state-changing endpoint
-
PersistServer processes follow/delete/mark action without CSRF validation
-
ImpactAccount state silently modified
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The victim must have an active authenticated session on the cti-transmute instance at the time they visit the attacker-controlled page - unauthenticated users cannot be exploited since the endpoints require authentication. Exploitation is limited to four specific account operations: following a user, deleting a notification, marking a single notification read, and marking all notifications read; no higher-privilege actions (account deletion, data export, configuration changes) are reachable via this vector. The cti-transmute web instance must be reachable from the victim's browser (same network, or internet-facing), since the attack runs in the victim's browser context. SameSite cookie policy set to Strict would block this attack entirely; Lax would block it for most sub-resource requests but not top-level navigations. The CVSS UI:P confirms that victim interaction (visiting an attacker page) is a hard prerequisite - passive network interception cannot trigger this vulnerability. |
| Impact | The CVSS 4.0 score of 5.3 (Medium) is consistent with the actual impact envelope: the vulnerability requires authenticated victim interaction (UI:P) and produces only low integrity impact (VI:L) - account social actions rather than data theft or system compromise. No EPSS data was provided in the intelligence feed, and this CVE is absent from CISA KEV, meaning no confirmed active exploitation. The attack is technically trivial to execute (a single crafted webpage suffices) but operationally constrained: the attacker cannot force the victim to visit their page and cannot exfiltrate data. For a CTI-sharing platform, unauthorized follows represent a social engineering surface - an attacker could silently follow targeted analysts to monitor activity - which elevates the contextual risk slightly beyond the raw CVSS. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P) accurately reflects that no special network positioning or configuration is required beyond inducing a page visit, and the absence of confidentiality impact (VC:N) is confirmed by the CSRF nature of the flaw, which cannot read responses cross-origin. |
| Exploit ScenarioDerived | An attacker registers an account on the cti-transmute instance and identifies their user_id, then embeds JavaScript in a phishing email or compromised webpage that silently issues a POST (or, pre-patch, a GET) to /account/follow?user_id=ATTACKER_ID when an authenticated analyst visits. The victim's browser sends the request with their active session cookie, causing the platform to record a follow relationship without the analyst's awareness. No public exploit code has been identified, but the attack surface is trivially constructable from the public commit diff. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Cross-site request forgery in MISP cti-transmute exposes four authenticated account endpoints - /account/follow, /account/delete_notification, /account/mark_notification_read, and /account/mark_all_read - to silent browser-driven invocation via malicious third-party pages. Because these state-changing operations were implemented as HTTP GET routes, any authenticated user visiting an attacker-controlled page could have follows added, notifications deleted, or notification state altered without consent. The fix (commit c352c2329e48ccc33a2b96d5353450cfbf7e89ec, reported by CIRCL) converts the routes to POST/DELETE and enforces X-CSRFToken header validation. No public exploit code has been identified and the vulnerability is not listed in CISA KEV.
RemediationAI
Apply the upstream patch available at https://github.com/MISP/cti-transmute/commit/c352c2329e48ccc33a2b96d5353450cfbf7e89ec, which converts /account/follow to POST, /account/delete_notification to DELETE, and /account/mark_notification_read and /account/mark_all_read to POST, with X-CSRFToken header enforcement added to all corresponding frontend fetch() calls. Operators should verify whether this fix has been incorporated into a tagged release and upgrade to that version; a specific patched release version was not independently confirmed from the available intelligence and should be verified against the MISP GitHub repository before deployment. As an interim compensating control, restricting access to the cti-transmute web interface to internal networks or requiring VPN authentication would prevent external attacker-controlled pages from being reachable by the victim's browser in a cross-site context, effectively neutralizing the CSRF vector. Enforcing SameSite=Strict or SameSite=Lax on session cookies would also block most CSRF GET-based attacks but should not substitute for the proper fix, as Lax mode still permits top-level navigation GET requests.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
MISP cti-transmute is a Flask-based Python web application (using Blueprints) that serves as a CTI format conversion and sharing companion to the MISP threat intelligence platform. The root cause is CWE-352 (Cross-Site Request Forgery): HTTP GET is an idempotent, 'safe' method that browsers replay automatically for resource fetches (img tags, link prefetch, navigations), making it unsuitable for state-changing operations. Without a CSRF token or SameSite cookie enforcement, any cross-origin page can trigger these endpoints with the victim's active session credentials. The CPE cpe:2.3:a:misp:cti-transmute:*:*:*:*:*:*:*:* confirms all versions prior to the patch commit are affected. The commit diff shows the full remediation scope: Flask route decorators updated to POST/DELETE, and all frontend fetch() calls updated to include the X-CSRFToken header extracted from the DOM.
Know when Misp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Network-delivered CSRF requiring victim to visit attacker page (UI:R), no privileges needed to craft attack (PR:N), low integrity impact limited to account social actions, no confidentiality or availability impact.
Primary rating from Vendor (CIRCL).
CVSS VectorVendor: CIRCL
DescriptionCVE.org
Affected versions of MISP cti-transmute expose several state-changing account operations as GET requests:
* /account/follow
* /account/delete_notification
* /account/mark_notification_read
* /account/mark_all_read
These endpoints require authentication, but before the fix they could be invoked with simple GET requests. That makes them susceptible to cross-site request forgery because a third-party site can induce the victim’s browser to send authenticated GET requests automatically.
The patch converts the actions to POST or DELETE and updates the frontend to include an X-CSRFToken header, providing explicit CSRF protection for those state-changing operations.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
An issue was discovered in MISP 2.4.9x before 2.4.99. Rated high severity (CVSS 8.8), this vulnerability is remotely exp
An issue was discovered in MISP before 2.4.158. Rated critical severity (CVSS 9.8), this vulnerability is remotely explo
app/Controller/Component/IndexFilterComponent.php in MISP before 2.4.167 mishandles ordered_url_params and additional_de
SQL injection in MISP threat intelligence platform versions prior to 2.5.37 allows remote unauthenticated attackers to m
An issue was discovered in MISP before 2.4.158. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitab
MISP 2.4.172 mishandles different certificate file extensions in server sync. Rated high severity (CVSS 7.5), this vulne
In MISP before 2.4.148, app/Lib/Export/OpendataExport.php mishandles parameter data that is used in a shell_exec call. R
An issue was discovered in app/Controller/UsersController.php in MISP 2.4.92. Rated critical severity (CVSS 9.8), this v
An issue was discovered in MISP 2.4.128. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
MISP before 2.4.135 lacks an ACL check, related to app/Controller/GalaxyElementsController.php and app/Model/GalaxyEleme
app/View/Elements/genericElements/IndexTable/Fields/generic_field.ctp in MISP 2.4.144 does not sanitize certain data rel
MISP 2.4.148, in certain configurations, allows SQL injection via the app/Model/Log.php $conditions['org'] value. Rated
EUVD-2026-55994
GHSA-75j5-9v4m-c666
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB