{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-6965 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-6965 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-6965 is a medium-severity missing authorization vulnerability in sc0ttkclark Pods – Custom Content Types and Fields, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-6965 and fix it if it is affected.\n\nWhat it is: CVE-2023-6965 is a medium-severity missing authorization vulnerability in sc0ttkclark Pods – Custom Content Types and Fields, published on 9 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-6965 in the wild and no public exploit code.\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-2023-6965/ (Markdown: https://insights.sbomify.com/CVE-2023-6965/index.md)","id":"CVE-2023-6965","markdown":"https://insights.sbomify.com/CVE-2023-6965/index.md","name":"CVE-2023-6965","record":{"aliases":["GHSA-4h68-4rgv-j269"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated contributors can create pods and users with default roles due to missing authorization checks in the Pods WordPress plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[{"product":"pods","vendor":"podsfoundation"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"The Pods – Custom Content Types and Fields plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 3.0.10 (with the exception of 2.7.31.2, 2.8.23.2, 2.9.19.2). This is due to the fact that the plugin allows the use of a file inclusion feature via shortcode. This makes it possible for authenticated attackers, with contributor access or higher, to create pods and users (with default role).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Pods - Custom Content Types and Fields - Missing Authorization","id":"CVE-2023-6965","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"The Moneytizer \u003c= 9.6.3 - Missing Authorization via multiple AJAX actions","id":"CVE-2023-6966"},"packages":[],"prev":{"headline":"Server-side request forgery in Kadence Blocks — Page Builder Toolkit for Gutenberg Editor","id":"CVE-2023-6964"},"products":["Pods – Custom Content Types and Fields"],"published":"2024-04-09","related":[{"cvss_score":8.8,"headline":"Pods - Custom Content Types and Fields - Authenticated (Contributor+) SQL Injection via Shortcode","id":"CVE-2023-6967","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":8.8,"headline":"Pods - Custom Content Types and Fields - Authenticated (Contributor+) Remote Code Execution","id":"CVE-2023-6999","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":7.1,"headline":"WordPress Pods Plugin \u003c= 2.9.10.2 is vulnerable to Cross Site Request Forgery (CSRF)","id":"CVE-2023-23790","kev_date_added":null,"published":"2023-05-03"},{"cvss_score":6.1,"headline":"Pods – Custom Content Types and Fields \u003c 3.2.8.1 - Admin+ Stored XSS","id":"CVE-2024-11849","kev_date_added":null,"published":"2025-01-06"},{"cvss_score":5.4,"headline":"Pods \u003c 2.7.27 - Authenticated Stored Cross-Site Scripting (XSS)","id":"CVE-2021-24338","kev_date_added":null,"published":"2021-06-21"},{"cvss_score":5.4,"headline":"Pods \u003c 2.7.27 - Authenticated Stored Cross-Site Scripting (XSS)","id":"CVE-2021-24339","kev_date_added":null,"published":"2021-06-21"},{"cvss_score":4.8,"headline":"Pods \u003c 3.2.7.1 - Admin+ Stored XSS","id":"CVE-2024-9883","kev_date_added":null,"published":"2024-11-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["sc0ttkclark"]},"summary":"Authenticated contributors can create pods and users with default roles due to missing authorization checks in the Pods WordPress plugin.","url":"https://insights.sbomify.com/CVE-2023-6965/"}