IntrepidityWordPress extension · Intrepidity Project
CVE-2023-27634
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 allows arbitrary file upload in Shingo Intrepidity plugin <= 1.5.1 versions.
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 confidenceCSRF vulnerability in Shingo Intrepidity plugin versions 1.5.1 and below allows attackers to trick authenticated administrators into uploading arbitrary files by tricking a logged-in admin to visit a malicious site, enabling remote code execution if uploaded files are executable.
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
IntrepidityWordPress extension
<= 1.5.1CVSS 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 Shingo Intrepidity plugin is installedLocate the Shingo Intrepidity plugin in the Jenkins plugin directory (typically $JENKINS_HOME/plugins/) or query via Jenkins CLI: jenkins-cli.jar or Manage Plugins UIAffected if Plugin is present in the Jenkins instance
-
Determine installed plugin versionCheck the plugin's manifest file (META-INF/MANIFEST.MF) within the plugin .hpi file, or view version in Manage Plugins > Installed pageAffected if Version is 1.5.1 or lower
-
Confirm file upload feature is enabledVerify the Intrepidity plugin's file upload/build action is available on at least one Jenkins job - check job configuration pages for Intrepidity-related build stepsAffected if Any Jenkins job has Intrepidity upload actions configured
-
Verify CSRF protection on upload endpointExamine HTTP responses when accessing Intrepidity upload endpoints - check for presence of Jenkinscrumb or similar CSRF tokens in upload formsAffected if Upload forms lack CSRF token validation (no Jenkinscrumb field present in upload requests)
User is affected if Shingo Intrepidity plugin version 1.5.1 or lower is installed with any job configured to use its file upload functionality, and the upload endpoint lacks CSRF token protection.
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 dataUpgrade to Shingo Intrepidity plugin version >1.5.1 which implements anti-CSRF token validation on file upload endpoints.
Fix this in Intrepidity
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27634 — 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-27634 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