CWE-352

{
  "affected": [],
  "aliases": [
    "CVE-2016-1201"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2016-04-30T10:59:00Z",
    "severity": "HIGH"
  },
  "details": "Cross-site request forgery (CSRF) vulnerability in LOCKON EC-CUBE 3.0.0 through 3.0.9 allows remote attackers to hijack the authentication of administrators.",
  "id": "GHSA-xfxj-wc89-979c",
  "modified": "2025-04-12T12:59:19Z",
  "published": "2022-05-17T03:43:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-1201"
    },
    {
      "type": "WEB",
      "url": "https://www.ec-cube.net/info/weakness/201604"
    },
    {
      "type": "WEB",
      "url": "http://jvn.jp/en/jp/JVN73776243/index.html"
    },
    {
      "type": "WEB",
      "url": "http://jvndb.jvn.jp/jvndb/JVNDB-2016-000053"
    },
    {
      "type": "WEB",
      "url": "http://www.ec-cube.net/info/weakness/weakness.php?id=67"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/90515"
    }
  ],
  "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"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2023-44238"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-10-09T10:15:22Z",
    "severity": "HIGH"
  },
  "details": "Cross-Site Request Forgery (CSRF) vulnerability in Joakim Ling Remove slug from custom post type plugin \u003c=\u00a01.0.3 versions.",
  "id": "GHSA-xg3h-q5gf-6gg9",
  "modified": "2024-04-04T08:25:48Z",
  "published": "2023-10-09T12:30:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-44238"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/vulnerability/remove-slug-from-custom-post-type/wordpress-remove-slug-from-custom-post-type-plugin-1-0-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:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2026-32443"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-03-13T19:55:04Z",
    "severity": "MODERATE"
  },
  "details": "Cross-Site Request Forgery (CSRF) vulnerability in Josh Kohlbach Product Feed PRO for WooCommerce woo-product-feed-pro allows Cross Site Request Forgery.This issue affects Product Feed PRO for WooCommerce: from n/a through \u003c= 13.5.2.",
  "id": "GHSA-xg3w-r3f7-rx2p",
  "modified": "2026-03-13T21:31:50Z",
  "published": "2026-03-13T21:31:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32443"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Plugin/woo-product-feed-pro/vulnerability/wordpress-product-feed-pro-for-woocommerce-plugin-13-5-2-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:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2025-30617"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-03-24T14:15:34Z",
    "severity": "MODERATE"
  },
  "details": "Cross-Site Request Forgery (CSRF) vulnerability in takien Rewrite allows Cross Site Request Forgery. This issue affects Rewrite: from n/a through 0.2.1.",
  "id": "GHSA-xg53-rgc9-jmqc",
  "modified": "2026-04-01T18:34:01Z",
  "published": "2025-03-24T15:30:48Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-30617"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/rewrite/vulnerability/wordpress-rewrite-0-2-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:N",
      "type": "CVSS_V3"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2024-6230"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-07-30T06:15:03Z",
    "severity": "MODERATE"
  },
  "details": "The \u067e\u0644\u0627\u06af\u06cc\u0646 \u067e\u0631\u062f\u0627\u062e\u062a \u062f\u0644\u062e\u0648\u0627\u0647 WordPress plugin through 2.9.8 does not have CSRF check in place when resetting its form fields, which could allow attackers to make a logged in admin perform such action via a CSRF attack",
  "id": "GHSA-xg5j-69w2-9h88",
  "modified": "2026-01-02T21:30:21Z",
  "published": "2024-07-30T06:30:37Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-6230"
    },
    {
      "type": "WEB",
      "url": "https://wpscan.com/vulnerability/311e3c15-0f58-4f3b-91f8-0c62c0eea55e"
    }
  ],
  "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"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2025-23900"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-01-16T21:15:31Z",
    "severity": "HIGH"
  },
  "details": "Cross-Site Request Forgery (CSRF) vulnerability in Genkisan Genki Announcement allows Cross Site Request Forgery.This issue affects Genki Announcement: from n/a through 1.4.1.",
  "id": "GHSA-xg6m-ppmj-29wf",
  "modified": "2026-04-01T18:33:15Z",
  "published": "2025-01-16T21:31:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-23900"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/genki-announcement/vulnerability/wordpress-genki-announcement-plugin-1-4-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"
    }
  ]
}

{
  "affected": [],
  "aliases": [
    "CVE-2025-10588"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-10-22T07:15:32Z",
    "severity": "MODERATE"
  },
  "details": "The PixelYourSite \u2013 Your smart PIXEL (TAG) \u0026 API Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 11.1.2. This is due to missing or incorrect nonce validation on the adminEnableGdprAjax() function. This makes it possible for unauthenticated attackers to modify GDPR settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.",
  "id": "GHSA-xg72-j993-8h8h",
  "modified": "2025-12-18T18:30:28Z",
  "published": "2025-10-22T09:30:18Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-10588"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3379001/pixelyoursite"
    },
    {
      "type": "WEB",
      "url": "https://research.cleantalk.org/cve-2025-10588"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/53c25e24-fac6-404c-be6c-678a383b48a1?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"
    }
  ]
}

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 5.0.9"
      },
      "package": {
        "ecosystem": "Packagist",
        "name": "admidio/admidio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "5.0.10"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-47229"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-29T22:01:58Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "## Summary\n\n`modules/sso/clients.php` validates an `adm_csrf_token` on every state-changing branch except `enable`. The `enable` case loads the SAML or OIDC client by UUID, calls `$client-\u003eenable($enabled)`, and persists the new state with no token check. Because the action is reachable via plain GET parameters, a third-party page can trick an authenticated administrator into disabling (or silently re-enabling) any configured SAML or OIDC client. Disabling an SSO client breaks every downstream relying-party application that authenticates through it.\n\n## Details\n\n### Vulnerable Code\n\n`modules/sso/clients.php:84-115` \u2014 the file\u0027s other branches each begin with `SecurityUtils::validateCsrfToken($_POST[\u0027adm_csrf_token\u0027]);`, but `case \u0027enable\u0027:` does not:\n\n```php\ncase \u0027delete_oidc\u0027:\n    // check the CSRF token of the form against the session token\n    SecurityUtils::validateCsrfToken($_POST[\u0027adm_csrf_token\u0027]);\n\n    $oidcService = new OIDCService($gDb, $gCurrentUser);\n    $client = $oidcService-\u003egetClientFromUUID($getClientUUID);\n    $client-\u003edelete();\n    echo json_encode(array(\u0027status\u0027 =\u003e \u0027success\u0027));\n    break;\n\ncase \u0027enable\u0027:                                          // \u003c- no CSRF validation\n    $enabled = admFuncVariableIsValid($_GET, \u0027enabled\u0027, \u0027boolean\u0027);\n    $client = new SAMLClient($gDb);\n    $client-\u003ereadDataByUuid($getClientUUID);\n    if ($client-\u003eisNewRecord()) {\n        // Not a SAML record, so try OIDC:\n        $client = new OIDCClient($gDb);\n        $client-\u003ereadDataByUuid($getClientUUID);\n    }\n    if ($client-\u003eisNewRecord()) {\n        throw new Exception(\u0027SYS_SSO_INVALID_CLIENT\u0027);\n    }\n    $client-\u003eenable($enabled);\n    $client-\u003esave();\n    echo json_encode([\u0027success\u0027 =\u003e true]);\n    break;\n```\n\nThe `enable($enabled)` call is documented to set a single boolean column on the SAML / OIDC client row \u2014 `smc_enabled` for SAML, `ocl_enabled` for OIDC \u2014 and `save()` persists the change immediately. The handler accepts plain GET (`admFuncVariableIsValid($_GET, \u0027enabled\u0027, \u0027boolean\u0027)`), so a `\u003cimg src=...\u003e` or auto-submitting form is sufficient.\n\n### Exploitation Flow\n\n1. Attacker prepares a hostile page that loads (e.g.) `\u003cimg src=\"http://victim.example/modules/sso/clients.php?mode=enable\u0026uuid=\u003cknown-sso-client-uuid\u003e\u0026enabled=0\"\u003e`. The client UUID can be observed by anyone who has visited the SSO settings, by anyone who has crawled the SAML metadata endpoint, or by anyone with read access to the SSO clients table \u2014 but the value is also enumerable: an admin viewing the list of SSO clients in the UI exposes `data-uuid` attributes in the rendered HTML, and SSO metadata endpoints (e.g. `modules/sso/saml.php?metadata=1\u0026uuid=...`) confirm valid UUIDs by returning XML.\n2. An Admidio administrator visits the hostile page while logged in. The browser sends Admidio\u0027s session cookie (which does not set `SameSite=Strict`).\n3. The server runs `case \u0027enable\u0027:` as the admin, sets `smc_enabled=0` (or `ocl_enabled=0`), and replies `{\"success\":true}`.\n4. The configured SAML / OIDC client is now disabled. Every downstream application authenticating through it gets `SYS_SSO_INVALID_CLIENT` on its next AuthnRequest / token-endpoint call. The outage persists until an admin notices and toggles it back on.\n\nThe attacker can also flip the bit the other way: silently *re-enabling* a client that an admin had previously deactivated (perhaps because of a security concern with that relying party).\n\n## PoC\n\nTested on HEAD `c5cde53`. To produce a deterministic test target, an SSO client is provisioned directly in the DB:\n\n```\n# 0. seed a SAML client\nmariadb -h 127.0.0.1 -P 3399 -u admidio -p... admidio \u003c\u003c\u0027SQL\u0027\nINSERT INTO adm_saml_clients (smc_uuid, smc_org_id, smc_client_name, smc_acs_url, smc_enabled,\n                              smc_timestamp_create, smc_usr_id_create)\nVALUES (\u0027aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee\u0027, 1, \u0027Test SAML\u0027, \u0027https://app.example/acs\u0027, 1,\n        NOW(), 2);\nSQL\n\nmariadb ... admidio -e \"SELECT smc_uuid, smc_client_name, smc_enabled FROM adm_saml_clients WHERE smc_client_name=\u0027Test SAML\u0027;\"\nsmc_uuid                              smc_client_name  smc_enabled\naaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee  Test SAML        1\n\n# 1. CSRF lure \u2014 admin\u0027s browser, no token supplied, GET only\ncurl -b $admin_cookie -i \\\n  \"http://127.0.0.1:8085/modules/sso/clients.php?mode=enable\u0026uuid=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee\u0026enabled=0\"\nHTTP/1.1 200 OK\n{\"success\":true}\n\n# 2. observe the change\nmariadb ... admidio -e \"SELECT smc_enabled FROM adm_saml_clients WHERE smc_uuid=\u0027aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee\u0027;\"\nsmc_enabled\n0\n```\n\nThe change persists. The legitimate admin\u0027s UI continues to show the client as configured, but every SAML AuthnRequest fails until the bit is toggled back.\n\n## Impact\n\nIn an Admidio deployment that uses SSO for downstream relying parties, a CSRF lure targeted at an administrator results in:\n\n* **SSO outage** for whichever client UUID the attacker chose. Users who depend on `app1.example/sso` (or similar) cannot log in. The outage persists until a human admin notices and re-enables the client by hand.\n* **Stealthy re-activation** of a client the admin had previously deactivated for a security reason \u2014 for example, a relying party whose certificate had been compromised \u2014 by passing `enabled=1` instead of `0`.\n\nThe impact is limited to the SAML / OIDC `_enabled` column; nothing else in the SSO state machine is mutated by this branch. Confidentiality is not affected. Availability is partial (`A:L`) because only one client at a time is hit, and only the SSO path of that client. Integrity is `I:L` because the `_enabled` bit is the only mutated column. `UI:R` reflects the admin-must-visit requirement; `PR:N` because the attacker needs no Admidio credentials of their own.\n\n## Recommended Fix\n\nAdd the CSRF check and switch the trigger from GET to POST:\n\n```php\ncase \u0027enable\u0027:\n    // check the CSRF token of the form against the session token\n    SecurityUtils::validateCsrfToken($_POST[\u0027adm_csrf_token\u0027]);\n\n    if ($_SERVER[\u0027REQUEST_METHOD\u0027] !== \u0027POST\u0027) {\n        throw new Exception(\u0027SYS_INVALID_PAGE_VIEW\u0027);\n    }\n\n    $enabled = admFuncVariableIsValid($_POST, \u0027enabled\u0027, \u0027boolean\u0027);\n    $client = new SAMLClient($gDb);\n    $client-\u003ereadDataByUuid($getClientUUID);\n    if ($client-\u003eisNewRecord()) {\n        $client = new OIDCClient($gDb);\n        $client-\u003ereadDataByUuid($getClientUUID);\n    }\n    if ($client-\u003eisNewRecord()) {\n        throw new Exception(\u0027SYS_SSO_INVALID_CLIENT\u0027);\n    }\n    $client-\u003eenable($enabled);\n    $client-\u003esave();\n    echo json_encode([\u0027success\u0027 =\u003e true]);\n    break;\n```\n\nUpdate the JS call site that drives the enable/disable toggle to POST the form\u0027s CSRF token (the page already renders `adm_csrf_token`).\n\nA regression test should issue a `GET /modules/sso/clients.php?mode=enable\u0026uuid=\u003cx\u003e\u0026enabled=0` with an admin cookie but no token, and assert the response rejects the request and the client\u0027s `_enabled` column is unchanged.",
  "id": "GHSA-xg76-5qj2-2hhv",
  "modified": "2026-05-29T22:01:58Z",
  "published": "2026-05-29T22:01:58Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/Admidio/admidio/security/advisories/GHSA-xg76-5qj2-2hhv"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/Admidio/admidio"
    }
  ],
  "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"
    }
  ],
  "summary": "Admidio: CSRF in SSO client `enable` action toggles SAML/OIDC clients without token validation"
}

{
  "affected": [],
  "aliases": [
    "CVE-2014-2249"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2014-03-16T14:06:00Z",
    "severity": "MODERATE"
  },
  "details": "Cross-site request forgery (CSRF) vulnerability on Siemens SIMATIC S7-1500 CPU PLC devices with firmware before 1.5.0 and SIMATIC S7-1200 CPU PLC devices with firmware before 4.0 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.",
  "id": "GHSA-xgc5-jhvr-xfh8",
  "modified": "2022-05-17T04:48:26Z",
  "published": "2022-05-17T04:48:26Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2014-2249"
    },
    {
      "type": "WEB",
      "url": "https://cert-portal.siemens.com/productcert/pdf/ssa-456423.pdf"
    },
    {
      "type": "WEB",
      "url": "https://cert-portal.siemens.com/productcert/pdf/ssa-654382.pdf"
    },
    {
      "type": "WEB",
      "url": "http://ics-cert.us-cert.gov/advisories/ICSA-14-073-01"
    },
    {
      "type": "WEB",
      "url": "http://ics-cert.us-cert.gov/advisories/ICSA-14-079-02"
    },
    {
      "type": "WEB",
      "url": "http://www.siemens.com/innovation/pool/de/forschungsfelder/siemens_security_advisory_ssa-456423.pdf"
    },
    {
      "type": "WEB",
      "url": "http://www.siemens.com/innovation/pool/de/forschungsfelder/siemens_security_advisory_ssa-654382.pdf"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

{
  "affected": [],
  "aliases": [
    "CVE-2019-15645"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-352"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2019-08-27T12:15:00Z",
    "severity": "HIGH"
  },
  "details": "The zoho-salesiq plugin before 1.0.9 for WordPress has CSRF.",
  "id": "GHSA-xgf3-3873-jq4x",
  "modified": "2024-04-04T01:49:03Z",
  "published": "2022-05-24T16:54:57Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-15645"
    },
    {
      "type": "WEB",
      "url": "https://wordpress.org/plugins/zoho-salesiq/#developers"
    },
    {
      "type": "WEB",
      "url": "https://wpvulndb.com/vulnerabilities/9433"
    }
  ],
  "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"
    }
  ]
}