CVE-2026-103908 · Package
NO FIX YET
The AMP for WP plugin for WordPress, up to and including version 1.1.18, passes an unvalidated value to do_shortcode. An authenticated user with custom-level access or higher can run arbitrary WordPress shortcodes on the site.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the AMP for WP plugin at version 1.1.18 or earlier, where the 'ampforwp-cat-description' setting is enabled, which the source says is the default. Exposure requires an attacker who already holds a custom-level or higher account, so sites without such accounts carry less risk. Sites that do not run the plugin can skip it.
Not affected if no-custom-level-users, plugin-not-installed, version-above-1.1.18
Who cares amp-for-wp, wordpress, wordpress-plugin
No fix yet, per the sources.
The The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 1.1.18. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for authenticated attackers, with custom-level access and above, to execute arbitrary shortcodes. The vulnerable output block is gated by the 'ampforwp-cat-description' setting, which is enabled by default, meaning the vast majority of installations are affected without any additional configuration change.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.