{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-8938 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8938 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8938 is a medium-severity vulnerability in nakamura1458 auto making JSON-LD, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-8938 and fix it if it is affected.\n\nWhat it is: CVE-2026-8938 is a medium-severity vulnerability in nakamura1458 auto making JSON-LD, published on 27 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-8938 in the wild and no public exploit code.\n\nAffected product: nakamura1458 auto making JSON-LD. 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-8938/ (Markdown: https://insights.sbomify.com/CVE-2026-8938/index.md)","id":"CVE-2026-8938","markdown":"https://insights.sbomify.com/CVE-2026-8938/index.md","name":"CVE-2026-8938","record":{"aliases":["GHSA-fv67-52hv-4432"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can trick administrators into updating license settings and installing unauthorized pro features via CSRF.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The auto making JSON-LD plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 4.5.3. This is due to missing or incorrect nonce validation on the amJL_certification function. This makes it possible for unauthenticated attackers to update the plugin's license key option, and subsequently trigger license validation and pro feature installation on the victim site without the administrator's consent via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. Successful exploitation can trigger downstream calls to amJL_is_license_valid() and amJL_download_and_install_pro_features(), meaning the impact extends beyond a simple settings change to unauthorized installation of plugin components.","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":"auto making JSON-LD \u003c= 4.5.3 - Cross-Site Request Forgery to Plugin Certification Settings via Nonce Validation Bypass","id":"CVE-2026-8938","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Search Simple Fields \u003c= 0.2 - Cross-Site Request Forgery to Plugin Settings Update","id":"CVE-2026-8939"},"packages":[],"prev":{"headline":"Missing Authorization in GitLab","id":"CVE-2026-8937"},"products":["auto making JSON-LD"],"published":"2026-05-27","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-05-27","vendors":["nakamura1458"]},"summary":"Unauthenticated attackers can trick administrators into updating license settings and installing unauthorized pro features via CSRF.","url":"https://insights.sbomify.com/CVE-2026-8938/"}