dbcve.org
Amp For WpWordPress extension · Magazine3

CVE-2023-48321

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-30
Fix available
A fix is available. Upgrade to after 1.0.88.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Ahmed Kaludi, Mohammed Kaludi AMP for WP – Accelerated Mobile Pages allows Stored XSS.This issue affects AMP for WP – Accelerated Mobile Pages: from n/a through 1.0.88.1.

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 · moderate confidence

A Stored Cross-Site Scripting (XSS) vulnerability exists in the AMP for WP – Accelerated Mobile Pages WordPress plugin. The vulnerability allows malicious JavaScript code to be injected through user input that is not properly sanitized before being rendered in generated web pages, affecting versions up to and including 1.0.88.1.

MitigationThe primary remediation is to implement proper input sanitization and output encoding throughout the plugin's web page generation code. Until an official patch is available, consider disabling the plugin or restricting access to input fields.

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
Amp For WpWordPress extension
Affected:<= 1.0.88.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify AMP for WP plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/amp-for-wp or search for 'Accelerated Mobile Pages' in WP admin under Plugins
    Affected if The plugin directory or listing shows the AMP for WP plugin is present on the site
  2. Identify installed plugin version
    Open the plugin's main PHP file (usually in wp-content/plugins/amp-for-wp/) and look for the 'Version' header in the plugin comments, or check the readme.txt file for the 'Stable tag' value
    Affected if The version number is 1.0.88.1 or lower (any version up to and including 1.0.88.1)
  3. Confirm plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the AMP for WP plugin status shows as 'Active'
    Affected if The plugin is currently activated on the WordPress site
  4. Inspect page output for injected scripts
    View the source code of generated AMP pages (pages with /amp/ in URL path) and look for unexpected <script> tags or javascript: URIs in attributes like onclick, onerror, or href
    Affected if Malicious script tags appear in the rendered AMP page source that were not intentionally added by the site administrator

A site is affected if the AMP for WP plugin versions 1.0.88.1 or lower is installed and active, and user-supplied input can be reflected in generated AMP pages without proper 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 a release after 1.0.88.1
Interim mitigation

The primary remediation is to implement proper input sanitization and output encoding throughout the plugin's web page generation code. Until an official patch is available, consider disabling the plugin or restricting access to input fields.

Recommended fix Moderate confidence

1.0.88.2 or latest available version

  1. Log in to your WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'AMP for WP – Accelerated Mobile Pages' in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest version
  5. After updating, verify the plugin is running on version 1.0.88.2 or later
  6. Clear any caching plugins or server-side caches to ensure the patched version is served

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

Fix this in Amp For Wp Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-48321 — 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-2023-48321 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