{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19598 exists.","fix":"No fix has been published for CVE-2026-19598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19598 is a critical authentication bypass vulnerability in sc0ttkclark Pods – Custom Content Types and Fields, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-19598 and fix it if it is affected.\n\nWhat it is: CVE-2026-19598 is a critical authentication bypass vulnerability in sc0ttkclark Pods – Custom Content Types and Fields, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19598 exists.\n\nAffected product: sc0ttkclark Pods – Custom Content Types and Fields. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-19598/ (Markdown: https://insights.sbomify.com/CVE-2026-19598/index.md)","id":"CVE-2026-19598","markdown":"https://insights.sbomify.com/CVE-2026-19598/index.md","name":"CVE-2026-19598","record":{"aliases":["GHSA-hmmc-48gm-3645"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can bypass authorization checks in the Pods plugin to escalate privileges to Administrator or reset user passwords, leading to full site takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Privilege Escalation via Authorization Bypass in all versions up to, and including, 3.3.9. The vulnerability exists because the pods_admin AJAX router funnels every access check — including the method allowlist, nonce verification, login enforcement, and capability gate — through pods_error(), which under the JSON meta-box-loader compatibility path only writes failures to the PHP error log and returns false instead of terminating the request, rendering all guards ineffective.  This makes it possible for unauthenticated attackers to escalate their privileges to Administrator or overwrite the password of any user account, including the site owner's, enabling complete site takeover, or perform another administrator action.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-18","github_poc":4,"max_poc_stars":5,"metasploit":0,"nuclei":1,"refs":[{"date":"2026-09-05T20:03:34Z","kind":"github_poc","ref":"https://github.com/0xCyp1337/CVE-2026-19598-","stars":5,"title":null},{"date":"2026-08-18T15:16:05Z","kind":"github_poc","ref":"https://github.com/ksotaria1337/CVE-2026-19598","stars":1,"title":null},{"date":"2026-08-19T02:10:44Z","kind":"github_poc","ref":"https://github.com/DeadExpl0it/CVE-2026-19598-PoC","stars":1,"title":"Proof of Concept for CVE-2026-19598 affecting Pods \u003c= 3.3.9."},{"date":"2026-08-21T13:06:49Z","kind":"github_poc","ref":"https://github.com/sag-asab/CVE-2026-19598","stars":1,"title":"Custom Content Types and Fields plugin for WordPress"},{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-19598.yaml","stars":null,"title":"Pods \u003c= 3.3.9 - Unauthenticated Privilege Escalation via pods_admin AJAX Router"}],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in Pods – Custom Content Types and Fields","id":"CVE-2026-19598","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Remote Code Execution vulnerability","id":"CVE-2026-19599"},"packages":[],"prev":{"headline":"OpenNMS XML collector XXE allows arbitrary file read from the OpenNMS host","id":"CVE-2026-19596"},"products":["Pods – Custom Content Types and Fields"],"published":"2026-08-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-17","vendors":["sc0ttkclark"]},"summary":"Unauthenticated attackers can bypass authorization checks in the Pods plugin to escalate privileges to Administrator or reset user passwords, leading to full site takeover.","url":"https://insights.sbomify.com/CVE-2026-19598/"}