CVE-2026-8938: CWE-352 Cross-Site Request Forgery (CSRF) in nakamura1458 auto making JSON-LD
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.
AI Analysis
Technical Summary
CVE-2026-8938 is a CSRF vulnerability in the auto making JSON-LD WordPress plugin caused by missing or incorrect nonce validation on the amJL_certification function. This flaw enables attackers to forge requests that update the plugin's license key and trigger license validation and pro feature installation without administrator consent. The vulnerability affects all versions up to and including 4.5.3. The CVSS 3.1 base score is 4.3, indicating medium severity, with attack vector network, low attack complexity, no privileges required, and user interaction required. No patch or official fix has been published as of the data provided.
Potential Impact
Successful exploitation allows an attacker to update the plugin's license key option and trigger unauthorized license validation and installation of pro features on the victim WordPress site. This could result in unauthorized changes to plugin components without administrator approval. There is no indication of direct confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should exercise caution to avoid clicking on untrusted links and consider restricting administrative access or implementing additional CSRF protections at the site level.
CVE-2026-8938: CWE-352 Cross-Site Request Forgery (CSRF) in nakamura1458 auto making JSON-LD
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.
CVSS v3.1
Score 4.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-8938 is a CSRF vulnerability in the auto making JSON-LD WordPress plugin caused by missing or incorrect nonce validation on the amJL_certification function. This flaw enables attackers to forge requests that update the plugin's license key and trigger license validation and pro feature installation without administrator consent. The vulnerability affects all versions up to and including 4.5.3. The CVSS 3.1 base score is 4.3, indicating medium severity, with attack vector network, low attack complexity, no privileges required, and user interaction required. No patch or official fix has been published as of the data provided.
Potential Impact
Successful exploitation allows an attacker to update the plugin's license key option and trigger unauthorized license validation and installation of pro features on the victim WordPress site. This could result in unauthorized changes to plugin components without administrator approval. There is no indication of direct confidentiality or availability impact. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, administrators should exercise caution to avoid clicking on untrusted links and consider restricting administrative access or implementing additional CSRF protections at the site level.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-19T12:01:19.071Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a169066e29bf47b509e1812
Added to database: 5/27/2026, 6:34:14 AM
Last enriched: 5/27/2026, 6:49:02 AM
Last updated: 5/28/2026, 8:54:36 PM
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.