dbcve.org
Pwa For Wp \& AmpWordPress extension · Magazine3

CVE-2024-47318

HIGH · 8.8 CVSS v3.1 Published 2024-11-01
Fix available
A fix is available. Upgrade to 1.7.73 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Missing Authorization vulnerability in Magazine3 PWA for WP & AMP pwa-for-wp.This issue affects PWA for WP & AMP: from n/a through <= 1.7.72.

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

This is a missing authorization (broken access control) vulnerability in the PWA for WP & AMP WordPress plugin. The plugin fails to properly verify user permissions before allowing access to certain functionality, potentially allowing lower-privileged users to perform actions reserved for administrators. With a CVSS of 8.8, this represents a significant security gap that could lead to unauthorized configuration changes or data access.

MitigationUpdate the PWA for WP & AMP plugin to version 1.7.73 or later, which should contain the vendor's authorization fix. If immediate updating is not feasible, temporarily restrict admin access to the plugin settings and monitor for unauthorized configuration changes.

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
Pwa For Wp \& AmpWordPress extension
Affected:< 1.7.73

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check the installed plugin version
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and locate 'PWA for WP & AMP' by Magazine3. Note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/pwa-for-wp/readme.txt or the main plugin PHP file.
    Affected if The installed version is less than 1.7.73
  2. Verify non-administrator user accounts exist
    Navigate to Users > Users List in the WordPress admin. Identify if there are any users assigned roles below Administrator (such as Editor, Author, Contributor, or Subscriber).
    Affected if There are non-administrator user accounts present in the WordPress installation
  3. Test access to plugin settings with limited privileges
    Log out and log back in using a non-administrator account. Attempt to access the PWA for WP & AMP settings page (typically found under Settings > PWA or a dedicated PWA admin menu item). Observe whether the settings interface loads without being blocked.
    Affected if A non-administrator user can access the plugin settings page without receiving an authorization error

Your environment is affected if the PWA for WP & AMP plugin version is below 1.7.73 and your WordPress site has non-administrator users who can access the plugin settings without proper permission checks.

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.7.73 or later
Fixed in 1.7.73
Interim mitigation

Update the PWA for WP & AMP plugin to version 1.7.73 or later, which should contain the vendor's authorization fix. If immediate updating is not feasible, temporarily restrict admin access to the plugin settings and monitor for unauthorized configuration changes.

Recommended fix High confidence

1.7.73

  1. 1. Back up your WordPress database and files before making any changes
  2. 2. Navigate to your WordPress admin dashboard > Plugins
  3. 3. Locate 'PWA for WP & AMP' in your installed plugins list
  4. 4. If an update is available, click 'Update Now' to upgrade to version 1.7.73
  5. 5. Alternatively, you can manually download version 1.7.73 from the WordPress plugin repository and upload it via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin is running version 1.7.73 in the Plugins list
  7. 7. Test your PWA functionality to ensure the update did not break existing features
Caveat Point release upgrade; minimal risk, but test PWA functionality after update

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

Fix this in Pwa For Wp \& Amp Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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