FoldersApplication · Jenkins
CVE-2023-40336
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 · uneditedA cross-site request forgery (CSRF) vulnerability in Jenkins Folders Plugin 6.846.v23698686f0f6 and earlier allows attackers to copy folders.
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 confidenceA cross-site request forgery (CSRF) vulnerability in Jenkins Folders Plugin versions 6.846.v23698686f0f6 and earlier allows authenticated Jenkins users to be tricked into copying folders via maliciously crafted web requests. Attackers can exploit this by luring authenticated users to visit crafted pages that automatically trigger the folder copy action.
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
FoldersApplication
<= 6.846.v23698686f0f6CVSS 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 Jenkins Folders Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Folders' in the list of installed pluginsAffected if The Folders plugin is not listed in installed plugins, meaning the vulnerability does not apply
-
Check the installed version of Folders PluginIn the same plugin list, note the version number displayed next to the Folders pluginAffected if The version shown is 6.846.v23698686f0f6 or earlier (any version up to and including this one)
-
Determine if folder copy functionality is accessibleAs an authenticated user with appropriate permissions, attempt to access or view the folder copy option (typically via folder context menu or actions menu in Jenkins UI)Affected if Authenticated users with folder create/copy permissions exist in the environment and folder copy feature is accessible to them
User is affected if Jenkins Folders Plugin version 6.846.v23698686f0f6 or earlier is installed AND authenticated users with folder copy permissions exist in the environment.
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 Jenkins Folders Plugin to a version newer than 6.846.v23698686f0f6. Ensure Jenkins global CSRF protection is enabled (default setting) as an additional defense-in-depth measure.
Latest version available in Jenkins Plugin Index (newer than 6.846.v23698686f0f6)
- Log in to Jenkins as an administrator
- Navigate to Manage Jenkins
- Click on Manage Plugins
- Go to the Updates tab
- Locate the 'Folders' plugin in the list
- Check the plugin checkbox
- Click 'Download now and install after restart' or 'Update'
- After download completes, restart Jenkins to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Folders
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-40336 — 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-40336 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