Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-wjmq-rpqq-w4h9

Jenkins Gitee Plugin missing permission checks

CVSS 5.4 MediumEPSS 0.0023 · 13th percentile

Published by the GitHub Advisory Database at 24 Jun 2026, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.jenkins-ci.plugins:giteeMaven<1292.v2559f2f3f2c01292.v2559f2f3f2c0
Identifiers
GHSA-wjmq-rpqq-w4h9 · CVE-2026-57291
Weakness (CWE)
CWE-862
Tags
Published
24 Jun 2026
Updated
25 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Jenkins Gitee Plugin versions 1288.v18b_deb_c9069b_ and earlier, and earlier than 1292.v2559f2f3f2c0, lack permission checks in several HTTP form validation endpoints for its global configuration. An attacker with Overall/Read permission could make Jenkins connect to an attacker-specified URL using credential IDs they obtained elsewhere, capturing stored credentials; the endpoints also accept non-POST requests, enabling cross-site request forgery. Upgrade to Jenkins Gitee Plugin 1292.v2559f2f3f2c0 or later, which adds the required permission checks and requires POST requests.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0023, the 13th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:16 UTC First seen by agentprime
  2. 31 Oct 2026, 14:16 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.