dbcve.org
Integrate Google DriveWordPress extension · Softlabbd

CVE-2023-47548

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-07
Fix available
A fix is available. Upgrade to 1.3.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
URL Redirection to Untrusted Site ('Open Redirect') vulnerability in SoftLab Integrate Google Drive – Browse, Upload, Download, Embed, Play, Share, Gallery, and Manage Your Google Drive Files Into Your WordPress Site.This issue affects Integrate Google Drive – Browse, Upload, Download, Embed, Play, Share, Gallery, and Manage Your Google Drive Files Into Your WordPress Site: from n/a through 1.3.2.

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

Open redirect vulnerability in SoftLab's WordPress Google Drive integration plugin allows attackers to craft malicious URLs that redirect users to external untrusted sites, potentially facilitating phishing attacks. The vulnerability affects all versions up to and including 1.3.2.

MitigationApply vendor patch/upgrade to the latest version of the plugin once released, and implement server-side validation of redirect parameters to ensure they remain within the expected domain.

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
Integrate Google DriveWordPress extension
Affected:< 1.3.3

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the plugin installation directory
    Check your WordPress wp-content/plugins/ folder for a directory named 'softlabbd-integrate-google-drive', 'softlab-google-drive', or similar naming pattern containing 'google drive' from Softlabbd.
    Affected if The plugin directory exists in the plugins folder
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually the one matching the directory name) and locate the plugin header comment containing 'Version:' or check the WordPress Plugins admin page for the version number.
    Affected if The installed version is 1.3.2 or lower (any version before 1.3.3)
  3. Verify the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and confirm the SoftLab Google Drive plugin shows as 'Active', or query the wp_options table for option_name 'active_plugins' containing the plugin slug.
    Affected if The plugin is currently active on the WordPress site
  4. Check for redirect-related functionality
    Search plugin files for redirect parameters, functions like 'wp_redirect', 'wp_safe_redirect', or query parameters named 'redirect', 'url', 'target', 'return' that might be used for open redirect.
    Affected if The plugin processes redirect parameters without validating they point to internal URLs only

You are affected if the SoftLab Google Drive plugin is installed, active, and running version 1.3.2 or lower, as these versions contain the open redirect vulnerability.

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.3.3 or later
Fixed in 1.3.3
Interim mitigation

Apply vendor patch/upgrade to the latest version of the plugin once released, and implement server-side validation of redirect parameters to ensure they remain within the expected domain.

Recommended fix Moderate confidence

Integrate Google Drive version 1.3.3

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Integrate Google Drive' in the plugin list
  4. Click 'Update now' if an update is available, or click 'Delete' and reinstall version 1.3.3
  5. Verify the plugin is running version 1.3.3 after the update

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

Fix this in Integrate Google Drive 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-2023-47548 — 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-47548 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