Googledrive Folder ListWordPress extension · Edush Maxim
CVE-2024-49335
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 sh4d0w28 GoogleDrive folder list googledrive-folder-list allows Stored XSS.This issue affects GoogleDrive folder list: from n/a through <= 2.2.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 · high confidenceCross-Site Request Forgery (CSRF) vulnerability in the GoogleDrive folder list Jenkins plugin allows remote attackers to inject malicious scripts through stored XSS. The lack of CSRF protection enables attackers to trick authenticated users into executing unintended actions that store malicious content, which then executes when other users view the affected pages.
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
Googledrive Folder ListWordPress extension
<= 2.2.2CVSS 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.
-
Verify GoogleDrive folder list plugin is installedIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, then search for 'GoogleDrive folder list' or 'Googledrive Folder List' to confirm the plugin is present.Affected if The plugin appears in the installed plugins list
-
Check installed plugin versionIn the Installed plugins list, locate the GoogleDrive folder list plugin and note the version number displayed in the Version column.Affected if The installed version is 2.2.2 or any version lower (e.g., 2.2.1, 2.2.0, 1.x)
-
Confirm plugin is actively configuredNavigate to the Jenkins job or folder configuration where the GoogleDrive folder list plugin is used. Look for a configuration section related to GoogleDrive or folder listing that pulls data from Google Drive.Affected if The plugin has an active job or folder configuration that references GoogleDrive as a data source
You are affected if the GoogleDrive folder list plugin is installed with version 2.2.2 or lower and has an active configuration that pulls folder listings from Google Drive, as this enables the CSRF-to-stored-XSS attack vector.
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 GoogleDrive folder list plugin to a version beyond 2.2.2 that includes CSRF protection and proper input sanitization to prevent stored XSS.
Fix this in Googledrive Folder List
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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 $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49335 — 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-2024-49335 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