Google AmpWordPress extension · Pixelative
CVE-2023-45831
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in Pixelative, Mohsin Rafique AMP WP – Google AMP For WordPress plugin <= 1.5.15 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the AMP WP WordPress plugin (versions 1.5.15 and below) allows attackers to trick authenticated administrators into performing unintended actions by forcing their browser to send malicious requests.
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
Google AmpWordPress extension
<= 1.5.15CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify AMP WP plugin is installedLog in to WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'AMP WP' or 'Pixelative Google Amp' in the list of active plugins.Affected if The plugin appears in the installed plugins list
-
Identify the installed versionIn the WordPress admin, go to Plugins > Installed Plugins. Click on the AMP WP plugin to view its details, or check the plugin's main PHP file (typically in /wp-content/plugins/amp-wp/) for the version constant in the header comment.Affected if The version displayed is 1.5.15 or lower
-
Compare version to affected rangeReview the version number found against the affected range: versions 1.5.15 and below.Affected if The installed version is 1.5.15 or any version below 1.5.15 (for example, 1.5.14, 1.5.10, 1.0.0)
-
Confirm administrator accounts existNavigate to Users > All Users in the WordPress admin panel to verify if any administrator-level accounts exist on the site.Affected if At least one administrator account exists on the WordPress site
The site is affected if the AMP WP plugin is installed with version 1.5.15 or below and the site has at least one administrator user account.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate the AMP WP plugin to version 1.5.16 or later to patch the CSRF vulnerability.
Latest version available on wordpress.org (version > 1.5.15)
- Navigate to WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate 'AMP WP – Google AMP For WordPress' by Pixelative/Mohsin Rafique
- Check the current version number to confirm it is <= 1.5.15
- Click 'Update now' if an update is available, or manually download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
- After updating, verify the plugin is running a version newer than 1.5.15
- Test critical administrative functions to ensure the update did not break site functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Google Amp
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-45831 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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