{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-115224 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-115224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-115224 is a medium-severity vulnerability in Unknown Customer Engagement System, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-115224 and fix it if it is affected.\n\nWhat it is: CVE-2026-115224 is a medium-severity vulnerability in Unknown Customer Engagement System, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-115224 in the wild and no public exploit code.\n\nAffected product: Unknown Customer Engagement System. 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-115224/ (Markdown: https://insights.sbomify.com/CVE-2026-115224/index.md)","id":"CVE-2026-115224","markdown":"https://insights.sbomify.com/CVE-2026-115224/index.md","name":"CVE-2026-115224","record":{"aliases":["GHSA-66pc-wp83-p27g"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[],"cvss":{"score":4.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"The Customer Engagement System  WordPress plugin before 2.0.2 does not safely build the SQL statements that store a popup's page and category visibility rules, concatenating request-supplied ID values directly into an INSERT statement with no parameter binding or integer cast, allowing an authenticated administrator to inject arbitrary SQL and read the contents of the WordPress database.","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":"Smart Popup by Supsystic \u003c 2.0.2 - Admin+ SQLi via Popup Page/Category Binding","id":"CVE-2026-115224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Smart Popup by Supsystic \u003c 2.0.2 - Unauthenticated SSRF via MailChimp Groups Lookup","id":"CVE-2026-115225"},"packages":[],"prev":{"headline":"Smart Popup by Supsystic \u003c 2.0.2 - Admin+ SSTI via Popup Text Block","id":"CVE-2026-115223"},"products":["Customer Engagement System"],"published":"2026-10-28","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-115224/"}