dbcve.org
Accelerated Mobile PagesWordPress extension · Ampforwp

CVE-2024-11254

MEDIUM · 6.1 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 1.1.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The AMP for WP – Accelerated Mobile Pages plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the disqus_name parameter in all versions up to, and including, 1.1.1 due to insufficient input validation. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The AMP for WP plugin for WordPress versions up to 1.1.1 contains a reflected cross-site scripting (XSS) vulnerability in the disqus_name parameter. User-supplied input in this parameter is reflected back into the page output without proper sanitization or output encoding, allowing injection of arbitrary JavaScript. An unauthenticated attacker can exploit this by tricking a user into clicking a specially crafted URL.

MitigationUpdate to the latest version of the plugin once a patch is released. In the meantime, warn users to avoid clicking untrusted links. The vulnerable code path handling the disqus_name parameter should be identified and proper input validation and output encoding should be implemented.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Accelerated Mobile PagesWordPress extension
Affected:< 1.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and version
    Locate the Ampforwp Accelerated Mobile Pages plugin in your WordPress wp-content/plugins directory and read the main plugin file header to obtain the installed version number.
    Affected if The installed version is 1.1.1 or lower (anything below 1.1.2).
  2. Identify the disqus_name parameter handler
    Search the plugin source code for the disqus_name parameter to verify the vulnerable code path exists. Look for code that retrieves this parameter from the request (such as $_GET or $_POST) and outputs it directly into HTML.
    Affected if The vulnerable code that processes the disqus_name parameter is present in the installed version.
  3. Determine if the vulnerable output is reachable
    Check whether the page or function that outputs the disqus_name parameter is accessible on your site. This typically occurs on AMP-enabled pages that include the Disqus comments feature.
    Affected if The page containing the vulnerable output is accessible to users (authenticated or unauthenticated).

You are affected if your installed plugin version is below 1.1.2 and the disqus_name parameter is being processed and reflected in page output without sanitization.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.2 or later
Fixed in 1.1.2
Interim mitigation

Update to the latest version of the plugin once a patch is released. In the meantime, warn users to avoid clicking untrusted links. The vulnerable code path handling the disqus_name parameter should be identified and proper input validation and output encoding should be implemented.

Recommended fix High confidence

AMP for WP plugin version 1.1.2

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Find 'AMP for WP – Accelerated Mobile Pages'
  4. 4. If update available, click 'Update Now' to version 1.1.2
  5. 5. Alternatively, download version 1.1.2 from wordpress.org/plugins/amp-for-wp and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the plugin is running version 1.1.2 after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Accelerated Mobile Pages Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-11254 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-11254 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data