CWE-352
AllowedCross-Site Request Forgery (CSRF)
Abstraction: Compound · Status: Stable
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
14173 vulnerabilities reference this CWE, most recent first.
GHSA-C72J-2FGM-89CC
Vulnerability from github – Published: 2022-05-17 19:57 – Updated: 2024-04-03 23:58The feature-comments plugin before 1.2.5 for WordPress has CSRF for featuring or burying a comment.
{
"affected": [],
"aliases": [
"CVE-2014-10382"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2019-08-22T20:15:00Z",
"severity": "MODERATE"
},
"details": "The feature-comments plugin before 1.2.5 for WordPress has CSRF for featuring or burying a comment.",
"id": "GHSA-c72j-2fgm-89cc",
"modified": "2024-04-03T23:58:44Z",
"published": "2022-05-17T19:57:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2014-10382"
},
{
"type": "WEB",
"url": "https://wordpress.org/plugins/feature-comments/#developers"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-C735-G9F2-2MVP
Vulnerability from github – Published: 2022-05-24 17:12 – Updated: 2024-03-12 16:01An extension point in Jenkins allows selectively disabling cross-site request forgery (CSRF) protection for specific URLs.
Implementations of that extension point received a different representation of the URL path than the Stapler web framework uses to dispatch requests in Jenkins 2.227 and earlier, LTS 2.204.5 and earlier. This discrepancy allowed attackers to craft URLs that would bypass the CSRF protection of any target URL.
Jenkins now uses the same representation of the URL path to decide whether CSRF protection is needed for a given URL as the Stapler web framework uses.
In case of problems, administrators can disable this security fix by setting the system property hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO to true.
As an additional safeguard, semicolon (;) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath to true.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.204.5"
},
"package": {
"ecosystem": "Maven",
"name": "org.jenkins-ci.main:jenkins-core"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2.204.6"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.227"
},
"package": {
"ecosystem": "Maven",
"name": "org.jenkins-ci.main:jenkins-core"
},
"ranges": [
{
"events": [
{
"introduced": "2.205"
},
{
"fixed": "2.228"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-2160"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-435"
],
"github_reviewed": true,
"github_reviewed_at": "2022-06-24T00:58:56Z",
"nvd_published_at": "2020-03-25T17:15:00Z",
"severity": "HIGH"
},
"details": "An extension point in Jenkins allows selectively disabling cross-site request forgery (CSRF) protection for specific URLs.\n\nImplementations of that extension point received a different representation of the URL path than the Stapler web framework uses to dispatch requests in Jenkins 2.227 and earlier, LTS 2.204.5 and earlier. This discrepancy allowed attackers to craft URLs that would bypass the CSRF protection of any target URL.\n\nJenkins now uses the same representation of the URL path to decide whether CSRF protection is needed for a given URL as the Stapler web framework uses.\n\nIn case of problems, administrators can disable this security fix by setting the system property `hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO` to `true`.\n\nAs an additional safeguard, semicolon (`;`) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property `jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath` to `true`.",
"id": "GHSA-c735-g9f2-2mvp",
"modified": "2024-03-12T16:01:44Z",
"published": "2022-05-24T17:12:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-2160"
},
{
"type": "WEB",
"url": "https://github.com/jenkinsci/jenkins/commit/f479652171f4ab854747de64b22bf59adb35fb8f"
},
{
"type": "WEB",
"url": "https://github.com/jenkinsci/jenkins/commit/f7cf28355973df1ca6eb19066370bf70b10742f7"
},
{
"type": "PACKAGE",
"url": "https://github.com/jenkinsci/jenkins"
},
{
"type": "WEB",
"url": "https://jenkins.io/security/advisory/2020-03-25/#SECURITY-1774"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2020/03/25/2"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Cross-Site Request Forgery in Jenkins"
}
GHSA-C73C-X77G-854R
Vulnerability from github – Published: 2026-05-12 15:34 – Updated: 2026-06-09 10:59OAuth State Validation Bypass via error Parameter Causes Local Server DoS in MCP Auth Callback
Description
The OpenClaude MCP authentication flow starts a temporary local HTTP server to handle OAuth callbacks. To prevent CSRF attacks, the server validates a state parameter against an internally stored value. However, due to a logic flaw in the order of conditionals, an attacker can completely bypass this check and force the server to shut down — without knowing the state value at all.
The vulnerable code looks like this:
if (!error && state !== oauthState) {
rejectOnce(new Error('OAuth state mismatch - possible CSRF attack'))
return
}
if (error) {
cleanup()
rejectOnce(new Error(errorMessage))
return
}
When a request arrives with an error query parameter (e.g., ?error=anything), the first condition becomes false because !error evaluates to false. This means the CSRF check is never reached. Execution falls through to the second block, where cleanup() is called — shutting down the local server and terminating the user's active authentication session.
The attacker does not need to know the state value. Any request containing an error parameter is enough to trigger the shutdown.
Impact
- The user's OAuth flow is silently terminated mid-session
- The local callback server is shut down (Denial of Service)
- Can be triggered remotely via a malicious web page using a cross-origin request (CSRF)
- No authentication or prior knowledge of the
statevalue is required
Steps to Reproduce
Save the following as poc.js and run with Node.js:
import { createServer } from 'http';
import { parse } from 'url';
const expectedState = "secure_state_abc123";
const server = createServer((req, res) => {
const parsedUrl = parse(req.url || '', true);
const { pathname, query } = parsedUrl;
const { state, error } = query;
if (pathname === '/callback') {
// Vulnerable: error param causes state check to be skipped entirely
if (!error && state !== expectedState) {
res.writeHead(400);
res.end('State mismatch');
console.log('[-] CSRF attempt blocked.');
return;
}
if (error) {
res.writeHead(200);
res.end(`Error: ${error}`);
console.log(`[!] Server shutting down. Triggered by: ${error}`);
server.close();
return;
}
}
});
server.listen(12345, '127.0.0.1', () => {
console.log('Listening on http://127.0.0.1:12345');
});
Terminal 1 — start the server:
node poc.js
Terminal 2 — trigger the bypass:
curl "http://127.0.0.1:12345/callback?error=triggered"
Expected result: Server shuts down immediately. The state value was never checked.
Root Cause
The CSRF protection is conditioned on !error, meaning it is silently disabled whenever an error parameter is present. The two checks need to be decoupled — state validation must happen first, independently of any other parameters.
Fix
Move the state check before the error check, and remove the dependency on !error:
// Fixed
if (state !== oauthState) {
cleanup()
rejectOnce(new Error('OAuth state mismatch - possible CSRF attack'))
return
}
if (error) {
cleanup()
rejectOnce(new Error(errorMessage))
return
}
With this change, any request — whether it contains an error parameter or not — must first pass the state validation before any further processing occurs.
Credit: Xanlar Agamalizade
{
"affected": [
{
"package": {
"ecosystem": "npm",
"name": "@gitlawb/openclaude"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.5.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-42073"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-05-12T15:34:30Z",
"nvd_published_at": "2026-06-02T17:16:31Z",
"severity": "MODERATE"
},
"details": "# OAuth State Validation Bypass via `error` Parameter Causes Local Server DoS in MCP Auth Callback\n---\n\n## Description\n\nThe OpenClaude MCP authentication flow starts a temporary local HTTP server to handle OAuth callbacks. To prevent CSRF attacks, the server validates a `state` parameter against an internally stored value. However, due to a logic flaw in the order of conditionals, an attacker can completely bypass this check and force the server to shut down \u2014 without knowing the `state` value at all.\n\nThe vulnerable code looks like this:\n\n```typescript\nif (!error \u0026\u0026 state !== oauthState) {\n rejectOnce(new Error(\u0027OAuth state mismatch - possible CSRF attack\u0027))\n return\n}\n\nif (error) {\n cleanup()\n rejectOnce(new Error(errorMessage))\n return\n}\n```\n\nWhen a request arrives with an `error` query parameter (e.g., `?error=anything`), the first condition becomes `false` because `!error` evaluates to `false`. This means the CSRF check is **never reached**. Execution falls through to the second block, where `cleanup()` is called \u2014 shutting down the local server and terminating the user\u0027s active authentication session.\n\nThe attacker does not need to know the `state` value. Any request containing an `error` parameter is enough to trigger the shutdown.\n\n---\n\n## Impact\n\n- The user\u0027s OAuth flow is silently terminated mid-session\n- The local callback server is shut down (Denial of Service)\n- Can be triggered remotely via a malicious web page using a cross-origin request (CSRF)\n- No authentication or prior knowledge of the `state` value is required\n\n---\n\n## Steps to Reproduce\n\nSave the following as `poc.js` and run with Node.js:\n\n```javascript\nimport { createServer } from \u0027http\u0027;\nimport { parse } from \u0027url\u0027;\n\nconst expectedState = \"secure_state_abc123\";\n\nconst server = createServer((req, res) =\u003e {\n const parsedUrl = parse(req.url || \u0027\u0027, true);\n const { pathname, query } = parsedUrl;\n const { state, error } = query;\n\n if (pathname === \u0027/callback\u0027) {\n\n // Vulnerable: error param causes state check to be skipped entirely\n if (!error \u0026\u0026 state !== expectedState) {\n res.writeHead(400);\n res.end(\u0027State mismatch\u0027);\n console.log(\u0027[-] CSRF attempt blocked.\u0027);\n return;\n }\n\n if (error) {\n res.writeHead(200);\n res.end(`Error: ${error}`);\n console.log(`[!] Server shutting down. Triggered by: ${error}`);\n server.close();\n return;\n }\n }\n});\n\nserver.listen(12345, \u0027127.0.0.1\u0027, () =\u003e {\n console.log(\u0027Listening on http://127.0.0.1:12345\u0027);\n});\n```\n\n**Terminal 1 \u2014 start the server:**\n```bash\nnode poc.js\n```\n\n**Terminal 2 \u2014 trigger the bypass:**\n```bash\ncurl \"http://127.0.0.1:12345/callback?error=triggered\"\n```\n\n**Expected result:** Server shuts down immediately. The `state` value was never checked.\n\n---\n\n## Root Cause\n\nThe CSRF protection is conditioned on `!error`, meaning it is silently disabled whenever an `error` parameter is present. The two checks need to be decoupled \u2014 state validation must happen first, independently of any other parameters.\n\n---\n\n## Fix\n\nMove the `state` check before the `error` check, and remove the dependency on `!error`:\n\n```typescript\n// Fixed\nif (state !== oauthState) {\n cleanup()\n rejectOnce(new Error(\u0027OAuth state mismatch - possible CSRF attack\u0027))\n return\n}\n\nif (error) {\n cleanup()\n rejectOnce(new Error(errorMessage))\n return\n}\n```\n\nWith this change, any request \u2014 whether it contains an `error` parameter or not \u2014 must first pass the state validation before any further processing occurs.\n\n---\n\nCredit: Xanlar Agamalizade",
"id": "GHSA-c73c-x77g-854r",
"modified": "2026-06-09T10:59:32Z",
"published": "2026-05-12T15:34:30Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/Gitlawb/openclaude/security/advisories/GHSA-c73c-x77g-854r"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42073"
},
{
"type": "WEB",
"url": "https://github.com/Gitlawb/openclaude/commit/739b8d1f40fde0e401a5cbd2b9a55d88bd5124ad"
},
{
"type": "PACKAGE",
"url": "https://github.com/Gitlawb/openclaude"
},
{
"type": "WEB",
"url": "https://github.com/Gitlawb/openclaude/releases/tag/v0.5.1"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "OpenClaude MCP OAuth Callback: State Check Bypass via error Param Leads to DoS"
}
GHSA-C73R-H28J-R6H3
Vulnerability from github – Published: 2025-10-14 15:31 – Updated: 2025-10-31 00:30A cross-site request forgery security issue exists in the product and version listed. The vulnerability stems from missing CSRF checks on the impacted form. This allows for unintended configuration modification if an attacker can convince a logged in admin to visit a crafted link.
{
"affected": [],
"aliases": [
"CVE-2025-7330"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-10-14T13:15:39Z",
"severity": "HIGH"
},
"details": "A cross-site request forgery security issue exists in the product and version listed. The vulnerability stems from missing CSRF checks on the impacted form. This allows for unintended configuration modification if an attacker can convince a logged in admin to visit a crafted link.",
"id": "GHSA-c73r-h28j-r6h3",
"modified": "2025-10-31T00:30:30Z",
"published": "2025-10-14T15:31:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-7330"
},
{
"type": "WEB",
"url": "https://www.rockwellautomation.com/en-us/trust-center/security-advisories/advisory.SD1756.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-C73R-J6J7-MFCH
Vulnerability from github – Published: 2025-02-07 12:31 – Updated: 2026-04-01 18:33Cross-Site Request Forgery (CSRF) vulnerability in ibasit GlobalQuran allows Cross Site Request Forgery. This issue affects GlobalQuran: from n/a through 1.0.
{
"affected": [],
"aliases": [
"CVE-2025-25143"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-02-07T10:15:19Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in ibasit GlobalQuran allows Cross Site Request Forgery. This issue affects GlobalQuran: from n/a through 1.0.",
"id": "GHSA-c73r-j6j7-mfch",
"modified": "2026-04-01T18:33:35Z",
"published": "2025-02-07T12:31:18Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-25143"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/globalquran/vulnerability/wordpress-globalquran-plugin-1-0-csrf-to-settings-change-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-C748-4MFM-3F26
Vulnerability from github – Published: 2025-11-18 09:30 – Updated: 2025-11-18 09:30The Top Friends plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.3. This is due to missing nonce validation on the top_friends_options_subpanel() function. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
{
"affected": [],
"aliases": [
"CVE-2025-12827"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-11-18T09:15:49Z",
"severity": "MODERATE"
},
"details": "The Top Friends plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 0.3. This is due to missing nonce validation on the top_friends_options_subpanel() function. This makes it possible for unauthenticated attackers to modify plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.",
"id": "GHSA-c748-4mfm-3f26",
"modified": "2025-11-18T09:30:52Z",
"published": "2025-11-18T09:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-12827"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/top-friends/tags/0.3/top-friends.php#L155"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/8165196d-0117-473f-8ccf-57ffd3e08e16?source=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-C76R-QXM5-V6H3
Vulnerability from github – Published: 2022-05-02 03:24 – Updated: 2022-05-02 03:24Cross-site request forgery (CSRF) vulnerability in TWiki before 4.3.1 allows remote authenticated users to hijack the authentication of arbitrary users for requests that update pages, as demonstrated by a URL for a save script in the SRC attribute of an IMG element, a related issue to CVE-2009-1434.
{
"affected": [],
"aliases": [
"CVE-2009-1339"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-04-30T20:30:00Z",
"severity": "MODERATE"
},
"details": "Cross-site request forgery (CSRF) vulnerability in TWiki before 4.3.1 allows remote authenticated users to hijack the authentication of arbitrary users for requests that update pages, as demonstrated by a URL for a save script in the SRC attribute of an IMG element, a related issue to CVE-2009-1434.",
"id": "GHSA-c76r-qxm5-v6h3",
"modified": "2022-05-02T03:24:11Z",
"published": "2022-05-02T03:24:11Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-1339"
},
{
"type": "WEB",
"url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/50254"
},
{
"type": "WEB",
"url": "https://launchpad.net/bugs/cve/2009-1339"
},
{
"type": "WEB",
"url": "http://bugs.debian.org/526258"
},
{
"type": "WEB",
"url": "http://secunia.com/advisories/34880"
},
{
"type": "WEB",
"url": "http://securitytracker.com/id?1022146"
},
{
"type": "WEB",
"url": "http://sourceforge.net/mailarchive/forum.php?thread_name=7E0723DC-CBFF-4DBD-B26C-8686287FF689%40twiki.net\u0026forum_name=twiki-announce"
},
{
"type": "WEB",
"url": "http://twiki.org/cgi-bin/view/Codev/SecurityAlert-CVE-2009-1339"
},
{
"type": "WEB",
"url": "http://twiki.org/p/pub/Codev/SecurityAlert-CVE-2009-1339/TWiki-4.3.0-c-diff-cve-2009-1339.txt"
},
{
"type": "WEB",
"url": "http://www.nabble.com/Bug-526258:-CVE-2009-1339:-CSRF-Vulnerability-with-Image-Tag-td23311575.html"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2009/1217"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-C7CJ-X2RM-37GQ
Vulnerability from github – Published: 2022-05-17 05:13 – Updated: 2022-05-17 05:13Multiple cross-site request forgery (CSRF) vulnerabilities in the web-based management utility on the NEC AtermWR9500N, AtermWR8600N, AtermWR8370N, AtermWR8160N, AtermWM3600R, and AtermWM3450RN routers allow remote attackers to hijack the authentication of administrators for requests that (1) initialize settings or (2) reboot the device.
{
"affected": [],
"aliases": [
"CVE-2013-0717"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2013-03-19T18:55:00Z",
"severity": "MODERATE"
},
"details": "Multiple cross-site request forgery (CSRF) vulnerabilities in the web-based management utility on the NEC AtermWR9500N, AtermWR8600N, AtermWR8370N, AtermWR8160N, AtermWM3600R, and AtermWM3450RN routers allow remote attackers to hijack the authentication of administrators for requests that (1) initialize settings or (2) reboot the device.",
"id": "GHSA-c7cj-x2rm-37gq",
"modified": "2022-05-17T05:13:24Z",
"published": "2022-05-17T05:13:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2013-0717"
},
{
"type": "WEB",
"url": "http://jpn.nec.com/security-info/secinfo/nv13-005.html"
},
{
"type": "WEB",
"url": "http://jvn.jp/en/jp/JVN59503133/6443/index.html"
},
{
"type": "WEB",
"url": "http://jvn.jp/en/jp/JVN59503133/index.html"
},
{
"type": "WEB",
"url": "http://jvndb.jvn.jp/jvndb/JVNDB-2013-000024"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-C7F5-5939-HQ32
Vulnerability from github – Published: 2025-03-28 12:31 – Updated: 2026-04-01 18:34Cross-Site Request Forgery (CSRF) vulnerability in Krzysztof Furtak KK I Like It allows Stored XSS. This issue affects KK I Like It: from n/a through 1.7.5.3.
{
"affected": [],
"aliases": [
"CVE-2025-31443"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-28T12:15:16Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Krzysztof Furtak KK I Like It allows Stored XSS. This issue affects KK I Like It: from n/a through 1.7.5.3.",
"id": "GHSA-c7f5-5939-hq32",
"modified": "2026-04-01T18:34:12Z",
"published": "2025-03-28T12:31:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31443"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/kk-i-like-it/vulnerability/wordpress-kk-i-like-it-plugin-1-7-5-3-csrf-to-stored-xss-vulnerability?_s_id=cve"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-C7FJ-697W-86J9
Vulnerability from github – Published: 2022-01-11 00:01 – Updated: 2022-01-15 00:03In Ultimaker S3 3D printer, Ultimaker S5 3D printer, Ultimaker 3 3D printer S-line through 6.3 and Ultimaker 3 through 5.2.16, the local webserver hosts APIs vulnerable to CSRF. They do not verify incoming requests.
{
"affected": [],
"aliases": [
"CVE-2021-34086"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2022-01-10T14:10:00Z",
"severity": "HIGH"
},
"details": "In Ultimaker S3 3D printer, Ultimaker S5 3D printer, Ultimaker 3 3D printer S-line through 6.3 and Ultimaker 3 through 5.2.16, the local webserver hosts APIs vulnerable to CSRF. They do not verify incoming requests.",
"id": "GHSA-c7fj-697w-86j9",
"modified": "2022-01-15T00:03:34Z",
"published": "2022-01-11T00:01:35Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-34086"
},
{
"type": "WEB",
"url": "https://kth.diva-portal.org/smash/get/diva2:1623489/FULLTEXT01.pdf"
},
{
"type": "WEB",
"url": "https://ultimaker.com/3d-printers/ultimaker-3"
},
{
"type": "WEB",
"url": "https://ultimaker.com/3d-printers/ultimaker-s3"
},
{
"type": "WEB",
"url": "https://ultimaker.com/3d-printers/ultimaker-s5"
}
],
"schema_version": "1.4.0",
"severity": []
}
Mitigation MIT-4
Strategy: Libraries or Frameworks
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
- For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
- Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
Mitigation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Mitigation
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
Mitigation
Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
Mitigation
- Use the "double-submitted cookie" method as described by Felten and Zeller:
- When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user's machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
- Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
- This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]
Mitigation
Do not use the GET method for any request that triggers a state change.
Mitigation
Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
CAPEC-111: JSON Hijacking (aka JavaScript Hijacking)
An attacker targets a system that uses JavaScript Object Notation (JSON) as a transport mechanism between the client and the server (common in Web 2.0 systems using AJAX) to steal possibly confidential information transmitted from the server back to the client inside the JSON object by taking advantage of the loophole in the browser's Same Origin Policy that does not prohibit JavaScript from one website to be included and executed in the context of another website.
CAPEC-462: Cross-Domain Search Timing
An attacker initiates cross domain HTTP / GET requests and times the server responses. The timing of these responses may leak important information on what is happening on the server. Browser's same origin policy prevents the attacker from directly reading the server responses (in the absence of any other weaknesses), but does not prevent the attacker from timing the responses to requests that the attacker issued cross domain.
CAPEC-467: Cross Site Identification
An attacker harvests identifying information about a victim via an active session that the victim's browser has with a social networking site. A victim may have the social networking site open in one tab or perhaps is simply using the "remember me" feature to keep their session with the social networking site active. An attacker induces a payload to execute in the victim's browser that transparently to the victim initiates a request to the social networking site (e.g., via available social network site APIs) to retrieve identifying information about a victim. While some of this information may be public, the attacker is able to harvest this information in context and may use it for further attacks on the user (e.g., spear phishing).
CAPEC-62: Cross Site Request Forgery
An attacker crafts malicious web links and distributes them (via web pages, email, etc.), typically in a targeted manner, hoping to induce users to click on the link and execute the malicious action against some third-party application. If successful, the action embedded in the malicious link will be processed and accepted by the targeted application with the users' privilege level. This type of attack leverages the persistence and implicit trust placed in user session cookies by many web applications today. In such an architecture, once the user authenticates to an application and a session cookie is created on the user's system, all following transactions for that session are authenticated using that cookie including potential actions initiated by an attacker and simply "riding" the existing session cookie.