Core Web Vitals \& Pagespeed BoosterWordPress extension · Magazine3
CVE-2023-35883
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 · uneditedURL Redirection to Untrusted Site ('Open Redirect') vulnerability in Magazine3 Core Web Vitals & PageSpeed Booster.This issue affects Core Web Vitals & PageSpeed Booster: from n/a through 1.0.12.
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 confidenceAn open redirect vulnerability exists in the Magazine3 Core Web Vitals & PageSpeed Booster WordPress plugin. Attackers can craft malicious URLs using the plugin to redirect users to attacker-controlled websites, potentially facilitating phishing attacks or malware delivery. The vulnerability affects all versions through 1.0.12.
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
Core Web Vitals \& Pagespeed BoosterWordPress extension
<= 1.0.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed plugin versionNavigate to WordPress admin > Plugins, find 'Magazine3 Core Web Vitals & PageSpeed Booster', and note the version number. Alternatively, check the plugin file header in wp-content/plugins/magazine3-wp-fastest-cache/ or similar plugin directory name containing 'magazine3' and 'wpspeed'Affected if Version listed is 1.0.12 or lower
-
Locate the plugin directoryList contents of wp-content/plugins/ directory and identify the exact folder name used for this plugin (may be magazine3-wp-fastest-cache, magazine3-speed-booster, or similar)Affected if Plugin directory exists in the plugins folder and contains the vulnerable code
-
Inspect redirect handling codeSearch plugin PHP files for redirect-related functions such as wp_redirect, wp_safe_redirect, or header() calls that accept user-controlled parameters like 'redirect', 'url', or 'target'Affected if Code accepts and processes redirect parameters without proper validation
-
Test for vulnerable redirect parameterIf the plugin exposes a URL parameter for redirection (common names: redirect, url, target, go, next), attempt a controlled test: append ?redirect=http://example.com to any page using the plugin and observe if a redirect occursAffected if The plugin performs a redirect to the supplied parameter value without sanitizing it against external domains
-
Review access logs for redirect exploitationSearch web server access logs (Apache error.log, Nginx access.log) for requests containing the plugin's redirect parameter pointing to external domains, for example: grep -i 'redirect=http' /var/log/apache2/access.logAffected if Log entries show requests with redirect parameters pointing to unfamiliar or suspicious external domains
You are affected if the plugin version is 1.0.12 or lower AND the plugin's redirect functionality is accessible via URL parameters without proper domain validation.
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 Magazine3 Core Web Vitals & PageSpeed Booster plugin to the latest version (1.0.13 or later) which contains the patched redirect logic. Review server access logs for suspicious redirect patterns prior to patching.
Fix this in Core Web Vitals \& Pagespeed Booster
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35883 — 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-35883 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