Skip to main content

CVE-2026-103908mohammed_kaludi AMP for WP – Accelerated Mobile Pages code injection

Low priorityMedium5.4EPSS not scored yet

CVE-2026-103908 is a code injection in mohammed_kaludi AMP for WP – Accelerated Mobile Pages, rated medium (5.4 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Deferred

What it is

Input is evaluated as code by the application, so an attacker's code runs inside it.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker run commands or code with the privileges of the affected service.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place mohammed_kaludi AMP for WP – Accelerated Mobile Pages runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. While there is no fix, review who holds accounts that can reach it.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
  • Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
  • Template engines. The flaw sits between untrusted input and code or command execution.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.

Questions to answer about your own systems

  • Where does mohammed_kaludi AMP for WP – Accelerated Mobile Pages run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.