{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15361 exists.","fix":"No fix has been published for CVE-2026-15361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15361 is a high-severity SQL injection vulnerability in Unknown Content Views, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-15361 and fix it if it is affected.\n\nWhat it is: CVE-2026-15361 is a high-severity SQL injection vulnerability in Unknown Content Views, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15361 exists.\n\nAffected product: Unknown Content Views. 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-15361/ (Markdown: https://insights.sbomify.com/CVE-2026-15361/index.md)","id":"CVE-2026-15361","markdown":"https://insights.sbomify.com/CVE-2026-15361/index.md","name":"CVE-2026-15361","record":{"aliases":["GHSA-gp8v-vc4r-wpf4"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Authenticated users can execute SQL injection attacks via an AJAX action due to missing capability checks and improper input sanitization.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The Content Views  WordPress plugin before 4.5 does not perform a capability check on one of its AJAX actions and does not properly sanitise attacker-supplied data before using it in a SQL query, allowing any authenticated user, including Subscribers, to perform SQL injection attacks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Content Views \u003c 4.5 - Subscriber+ SQL Injection via preview_request","id":"CVE-2026-15361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Kids Mode","id":"CVE-2026-15365"},"packages":[],"prev":{"headline":"Ajax Load More \u003c 8.0.1 - Unauthenticated SQL Injection via custom_args","id":"CVE-2026-15360"},"products":["Content Views"],"published":"2026-08-07","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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["Unknown"]},"summary":"Authenticated users can execute SQL injection attacks via an AJAX action due to missing capability checks and improper input sanitization.","url":"https://insights.sbomify.com/CVE-2026-15361/"}