{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49819 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-49819 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-49819 is a high-severity unsafe deserialization vulnerability in Gordon Böhme, Antonio Leutsch Structured Content (JSON-LD) #wpsc, published on 18 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49819 and fix it if it is affected.\n\nWhat it is: CVE-2023-49819 is a high-severity unsafe deserialization vulnerability in Gordon Böhme, Antonio Leutsch Structured Content (JSON-LD) #wpsc, published on 18 Dec 2023. 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-49819 in the wild and no public exploit code.\n\nAffected product: Gordon Böhme, Antonio Leutsch Structured Content (JSON-LD) #wpsc. 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-49819/ (Markdown: https://insights.sbomify.com/CVE-2023-49819/index.md)","id":"CVE-2023-49819","markdown":"https://insights.sbomify.com/CVE-2023-49819/index.md","name":"CVE-2023-49819","record":{"aliases":["GHSA-69m4-r76x-j23h"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"An attacker can exploit PHP object injection in the Structured Content plugin to potentially execute arbitrary code on the WordPress site.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[{"product":"structured_content","vendor":"wpsc-plugin"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Deserialization of Untrusted Data vulnerability in Gordon Böhme, Antonio Leutsch Structured Content (JSON-LD) #wpsc.This issue affects Structured Content (JSON-LD) #wpsc: from n/a through 1.5.3.","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":"WordPress Structured Content Plugin \u003c= 1.5.3 is vulnerable to PHP Object Injection","id":"CVE-2023-49819","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Structured Content Plugin \u003c= 1.5.3 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-49820"},"packages":[],"prev":{"headline":"WordPress Webflow Pages plugin \u003c= 1.0.8 - Broken Access Control vulnerability","id":"CVE-2023-49818"},"products":["Structured Content (JSON-LD) #wpsc"],"published":"2023-12-18","related":[{"cvss_score":6.5,"headline":"WordPress Structured Content Plugin \u003c= 1.6.1 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2024-24839","kev_date_added":null,"published":"2024-02-05"},{"cvss_score":6.5,"headline":"WordPress Structured Content Plugin \u003c= 1.5.3 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-49820","kev_date_added":null,"published":"2023-12-14"},{"cvss_score":6.4,"headline":"Cross-site scripting in Structured Content (JSON-LD) #wpsc","id":"CVE-2025-0512","kev_date_added":null,"published":"2025-03-04"},{"cvss_score":5.4,"headline":"Structured Content \u003c 1.5.1 - Contributor+ Stored XSS in Shortcode","id":"CVE-2022-4715","kev_date_added":null,"published":"2023-01-23"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Gordon Böhme, Antonio Leutsch"]},"summary":"An attacker can exploit PHP object injection in the Structured Content plugin to potentially execute arbitrary code on the WordPress site.","url":"https://insights.sbomify.com/CVE-2023-49819/"}