CVE-2025-62144
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 · uneditedMissing Authorization vulnerability in Mohammed Kaludi Core Web Vitals & PageSpeed Booster core-web-vitals-pagespeed-booster allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Core Web Vitals & PageSpeed Booster: from n/a through <= 1.0.28.
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 confidenceMissing authorization vulnerability in the Core Web Vitals & PageSpeed Booster WordPress plugin (versions up to 1.0.28) allows attackers to exploit incorrectly configured access control security levels, potentially enabling authenticated users to perform unauthorized actions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedIn the WordPress admin dashboard, go to Plugins > Installed Plugins and look for 'Core Web Vitals & PageSpeed Booster' in the list of active or installed plugins.Affected if The plugin appears in the installed plugins list.
-
Check the installed version numberIn the Plugins page, click on the plugin name or view details to locate the version number displayed under the plugin name.Affected if The installed version is 1.0.28 or any earlier version (versions up to and including 1.0.28 are affected).
-
Review user role access to plugin capabilitiesNavigate to the plugin settings or check WordPress user roles under Users > Roles. Examine which user roles (such as Administrator, Editor, Author, Contributor, or Subscriber) have access to the plugin's functionality or settings pages.Affected if Any user role other than Administrator has been granted access to the plugin settings or its configuration options, indicating a potential authorization misconfiguration.
-
Inspect plugin settings for authorization controlsAccess the plugin settings page (usually under Settings or a dedicated menu item named after the plugin) and look for options related to user permissions, capability requirements, or access control settings.Affected if The plugin allows configuration of access permissions and those settings permit lower-privileged users to modify plugin options.
The environment is affected if the Core Web Vitals & PageSpeed Booster plugin is installed at version 1.0.28 or lower, and any authenticated user role beyond Administrator can access or modify plugin settings.
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.
From vendor dataUpdate the plugin to the latest available version once a patch is released, or disable the plugin until a fix is available. Review user role capabilities as a temporary hardening measure.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62144 — 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-2025-62144 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