Monthly
Session hijacking via cross-site request forgery affects OpenHuman versions before 0.56.0: the unauthenticated loopback callback GET /auth/telegram accepts an attacker-supplied one-time Telegram login token and writes the returned JWT straight into the victim's local session store, switching the victim's active session to the attacker's backend account (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1 High). Because the malicious request is issued by the victim's own browser to 127.0.0.1:7788, the attacker needs only their own OpenHuman account, a valid one-time Telegram token, and a victim who visits a crafted page while their local core is running - no authentication to the victim host is required. Exploitation leaves subsequent agent actions, memory writes, and Telegram messages flowing into the attacker's account; no public exploit code or confirmed active exploitation was identified at time of analysis.
Cross-site request forgery in the aThemeArt Theme Helper WordPress plugin (all versions up to and including 1.0.8) allows a remote attacker with no credentials of their own (CVSS:3.1/AV:N/AC:L/PR:N) to induce a logged-in privileged WordPress user - typically an administrator - to submit a forged request to the site, causing state-changing plugin actions to execute with the victim's authority. The flaw is a missing CSRF token check (CWE-352); the forged action is limited to operations the plugin exposes without nonce validation, and exploitation hinges on the victim having an active authenticated session and being tricked into interacting with attacker-supplied content (UI:R). A Patchstack advisory is the only public reference, and no public exploit code or confirmed active exploitation has been identified at time of analysis. Note that the supplied CVSS 3.1 vector (8.8, C:H/I:H/A:H) is more severe than our independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L), which reflects that impact is bounded by the victim's privilege level and by which nonce-less plugin endpoints exist.
Cross-site request forgery in the Salon Booking System WordPress plugin (versions before 10.31.9) allows unauthenticated attackers to forge REST API requests in a logged-in administrator's browser by tricking the victim into clicking a crafted link, potentially leading to full site takeover via creation of a new administrator account. The flaw (CWE-352) stems from the plugin discarding WordPress core's nonce check for cookie-authenticated sessions across the entire REST API, so no plugin-specific feature toggle is needed beyond having the vulnerable version installed. Publicly available exploit code exists; EPSS is low at 0.11% (1st percentile), and there is no confirmed active exploitation (CISA KEV).
Cross-site request forgery in ConvertX versions prior to 0.18.0 lets an attacker permanently delete an authenticated user's conversion jobs by luring that user into loading attacker-controlled content that silently requests /delete/{id} over HTTP GET. Because the deletion route performs a state-changing action without a CSRF token and job identifiers are simple sequential integers, an <img> or <iframe> src pointing at a guessed id is enough to trigger deletion with the victim's session cookie attached, with no click required. Exploitation requires an active victim session and the victim viewing attacker-controlled content; impact is confined to the victim's own job history (the provider scores this 8.1 with I:H/A:H, while our assessment rates the impact as limited, I:L/A:L), no public exploit code has been identified, and CISA KEV does not list this issue. The flaw is fixed in version 0.18.0, which converts the endpoint to POST and switches the UI to form-based submission.
Cross-site request forgery in the Patreon WordPress plugin (slug patreon-connect) through version 1.9.17 allows an attacker to craft a request that a logged-in WordPress administrator may submit without intent, because the affected functionality lacks anti-CSRF nonce validation. The independent assessment rates this as integrity-only impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N), lower than the 8.1 score reported elsewhere, and notes that the signals are thin and partly conflicting; exploitation requires a logged-in privileged user (typically an administrator) to visit attacker-controlled content or click a crafted link. No public exploit code and no CISA KEV entry were identified at time of analysis, and the attacker gains only the privileges of the victimized session.
Cross-site request forgery in the Patreon WordPress plugin (patreon-connect), affecting all versions up to and including 1.10.0, allows an attacker to ride a logged-in user's browser session and trigger state-changing plugin requests that lack a valid anti-CSRF token. The CVSS vector (PR:N, UI:R) means the attacker needs no credentials of their own but must convince an authenticated user - typically a site administrator or other privileged account - to load attacker-controlled content while logged in; the realistic impact is unauthorized state modification rather than data theft or denial of service. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so there is no evidence of active exploitation; the Patchstack advisory is the only public reference.
Progress MarkLogic Server deployments in the 12.x line before 12.1.0 and the 11.x line before 11.3.7 generate predictable anti-CSRF tokens for Query Console, allowing a remote attacker to forge requests that pass CSRF validation and execute server-side code with the permissions of a logged-in victim. Exploitation is conditional: the attacker must lure a user who currently holds a live authenticated Query Console session to an attacker-controlled page, so user interaction is mandatory and unattended servers or logged-out users are not reachable this way. A vendor advisory is available (community.progress.com MarkLogic Critical Security Alert Bulletin, October 2026) and confirmed fixed versions exist; there is no CISA KEV entry and no public exploit code identified at time of analysis, and no EPSS score was supplied, so this is best treated as a credible but conditional risk rather than a drop-everything emergency.
Cross-site request forgery in OpenRefine through 3.10.1 lets a remote attacker run operating system commands as the OpenRefine user by luring that user's browser into issuing a crafted cross-origin GET to the local get-rows command with a malicious engine parameter that evaluates a Jython facet expression. Exploitation is not drive-by: it requires the victim to have OpenRefine running with a project loaded and an active session and to be induced into visiting an attacker-controlled page, and it depends on the target build bundling the Jython extension that provides the expression-evaluation path. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); the assessed CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects high attack complexity and mandatory user interaction offsetting the full confidentiality, integrity and availability impact on the OpenRefine host.
Cross-site request forgery in Nginx UI versions 2.0.0 through 2.4.x lets a remote attacker drive a logged-in administrator's browser into performing authenticated, state-changing management operations - including rewriting Nginx configuration through POST /api/configs, triggering config reloads, and invoking other admin endpoints - because the AuthRequired middleware accepts the browser-managed JWT cookie as a valid API credential while management routes generally enforce neither a CSRF token nor Origin/Referer validation. Exploitation requires the victim to be a currently logged-in administrator who is induced to visit an attacker-controlled page (UI:R); per the CVSS vector the attacker needs no credentials of their own (PR:N), but a targeted account protected by OTP/Passkey step-up, or an endpoint requiring secure-session proof, is not exploitable. The attacker cannot read cross-origin responses, so impact is blind configuration tampering and service disruption rather than data exfiltration; the issue is fixed in 2.5.0, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Cross-site request forgery in the WordPress plugin Dashboard Notes (MIGHTYminnow) affects all versions through 1.0.3, letting an attacker craft a page or link that silently rides an authenticated privileged user's session to perform state-changing plugin actions. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L (7.1) reflects that the attacker needs no server-side authentication (PR:N) but must successfully lure a logged-in user with access to the plugin's dashboard functionality into interacting with attacker-controlled content (UI:R); exploitation cannot occur without that victim action. No public exploit code and no confirmed active exploitation were identified at time of analysis, though the low attack complexity and the universal applicability of CSRF to unpatched WordPress plugins keep the practical risk meaningful for sites running 1.0.3 or earlier.
Session hijacking via cross-site request forgery affects OpenHuman versions before 0.56.0: the unauthenticated loopback callback GET /auth/telegram accepts an attacker-supplied one-time Telegram login token and writes the returned JWT straight into the victim's local session store, switching the victim's active session to the attacker's backend account (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, base 8.1 High). Because the malicious request is issued by the victim's own browser to 127.0.0.1:7788, the attacker needs only their own OpenHuman account, a valid one-time Telegram token, and a victim who visits a crafted page while their local core is running - no authentication to the victim host is required. Exploitation leaves subsequent agent actions, memory writes, and Telegram messages flowing into the attacker's account; no public exploit code or confirmed active exploitation was identified at time of analysis.
Cross-site request forgery in the aThemeArt Theme Helper WordPress plugin (all versions up to and including 1.0.8) allows a remote attacker with no credentials of their own (CVSS:3.1/AV:N/AC:L/PR:N) to induce a logged-in privileged WordPress user - typically an administrator - to submit a forged request to the site, causing state-changing plugin actions to execute with the victim's authority. The flaw is a missing CSRF token check (CWE-352); the forged action is limited to operations the plugin exposes without nonce validation, and exploitation hinges on the victim having an active authenticated session and being tricked into interacting with attacker-supplied content (UI:R). A Patchstack advisory is the only public reference, and no public exploit code or confirmed active exploitation has been identified at time of analysis. Note that the supplied CVSS 3.1 vector (8.8, C:H/I:H/A:H) is more severe than our independent assessment (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L), which reflects that impact is bounded by the victim's privilege level and by which nonce-less plugin endpoints exist.
Cross-site request forgery in the Salon Booking System WordPress plugin (versions before 10.31.9) allows unauthenticated attackers to forge REST API requests in a logged-in administrator's browser by tricking the victim into clicking a crafted link, potentially leading to full site takeover via creation of a new administrator account. The flaw (CWE-352) stems from the plugin discarding WordPress core's nonce check for cookie-authenticated sessions across the entire REST API, so no plugin-specific feature toggle is needed beyond having the vulnerable version installed. Publicly available exploit code exists; EPSS is low at 0.11% (1st percentile), and there is no confirmed active exploitation (CISA KEV).
Cross-site request forgery in ConvertX versions prior to 0.18.0 lets an attacker permanently delete an authenticated user's conversion jobs by luring that user into loading attacker-controlled content that silently requests /delete/{id} over HTTP GET. Because the deletion route performs a state-changing action without a CSRF token and job identifiers are simple sequential integers, an <img> or <iframe> src pointing at a guessed id is enough to trigger deletion with the victim's session cookie attached, with no click required. Exploitation requires an active victim session and the victim viewing attacker-controlled content; impact is confined to the victim's own job history (the provider scores this 8.1 with I:H/A:H, while our assessment rates the impact as limited, I:L/A:L), no public exploit code has been identified, and CISA KEV does not list this issue. The flaw is fixed in version 0.18.0, which converts the endpoint to POST and switches the UI to form-based submission.
Cross-site request forgery in the Patreon WordPress plugin (slug patreon-connect) through version 1.9.17 allows an attacker to craft a request that a logged-in WordPress administrator may submit without intent, because the affected functionality lacks anti-CSRF nonce validation. The independent assessment rates this as integrity-only impact (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N), lower than the 8.1 score reported elsewhere, and notes that the signals are thin and partly conflicting; exploitation requires a logged-in privileged user (typically an administrator) to visit attacker-controlled content or click a crafted link. No public exploit code and no CISA KEV entry were identified at time of analysis, and the attacker gains only the privileges of the victimized session.
Cross-site request forgery in the Patreon WordPress plugin (patreon-connect), affecting all versions up to and including 1.10.0, allows an attacker to ride a logged-in user's browser session and trigger state-changing plugin requests that lack a valid anti-CSRF token. The CVSS vector (PR:N, UI:R) means the attacker needs no credentials of their own but must convince an authenticated user - typically a site administrator or other privileged account - to load attacker-controlled content while logged in; the realistic impact is unauthorized state modification rather than data theft or denial of service. No public exploit code has been identified at time of analysis, and the issue is not listed in CISA KEV, so there is no evidence of active exploitation; the Patchstack advisory is the only public reference.
Progress MarkLogic Server deployments in the 12.x line before 12.1.0 and the 11.x line before 11.3.7 generate predictable anti-CSRF tokens for Query Console, allowing a remote attacker to forge requests that pass CSRF validation and execute server-side code with the permissions of a logged-in victim. Exploitation is conditional: the attacker must lure a user who currently holds a live authenticated Query Console session to an attacker-controlled page, so user interaction is mandatory and unattended servers or logged-out users are not reachable this way. A vendor advisory is available (community.progress.com MarkLogic Critical Security Alert Bulletin, October 2026) and confirmed fixed versions exist; there is no CISA KEV entry and no public exploit code identified at time of analysis, and no EPSS score was supplied, so this is best treated as a credible but conditional risk rather than a drop-everything emergency.
Cross-site request forgery in OpenRefine through 3.10.1 lets a remote attacker run operating system commands as the OpenRefine user by luring that user's browser into issuing a crafted cross-origin GET to the local get-rows command with a malicious engine parameter that evaluates a Jython facet expression. Exploitation is not drive-by: it requires the victim to have OpenRefine running with a project loaded and an active session and to be induced into visiting an attacker-controlled page, and it depends on the target build bundling the Jython extension that provides the expression-evaluation path. There is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV); the assessed CVSS:3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects high attack complexity and mandatory user interaction offsetting the full confidentiality, integrity and availability impact on the OpenRefine host.
Cross-site request forgery in Nginx UI versions 2.0.0 through 2.4.x lets a remote attacker drive a logged-in administrator's browser into performing authenticated, state-changing management operations - including rewriting Nginx configuration through POST /api/configs, triggering config reloads, and invoking other admin endpoints - because the AuthRequired middleware accepts the browser-managed JWT cookie as a valid API credential while management routes generally enforce neither a CSRF token nor Origin/Referer validation. Exploitation requires the victim to be a currently logged-in administrator who is induced to visit an attacker-controlled page (UI:R); per the CVSS vector the attacker needs no credentials of their own (PR:N), but a targeted account protected by OTP/Passkey step-up, or an endpoint requiring secure-session proof, is not exploitable. The attacker cannot read cross-origin responses, so impact is blind configuration tampering and service disruption rather than data exfiltration; the issue is fixed in 2.5.0, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Cross-site request forgery in the WordPress plugin Dashboard Notes (MIGHTYminnow) affects all versions through 1.0.3, letting an attacker craft a page or link that silently rides an authenticated privileged user's session to perform state-changing plugin actions. The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L (7.1) reflects that the attacker needs no server-side authentication (PR:N) but must successfully lure a logged-in user with access to the plugin's dashboard functionality into interacting with attacker-controlled content (UI:R); exploitation cannot occur without that victim action. No public exploit code and no confirmed active exploitation were identified at time of analysis, though the low attack complexity and the universal applicability of CSRF to unpatched WordPress plugins keep the practical risk meaningful for sites running 1.0.3 or earlier.