How severe is GHSA-xxhf-xq6v-c8mj?

GHSA-xxhf-xq6v-c8mj has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xxhf-xq6v-c8mj?

GHSA-xxhf-xq6v-c8mj affects the following packages: org.jenkins-ci.plugins:embeddable-build-status (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xxhf-xq6v-c8mj?

Update org.jenkins-ci.plugins:embeddable-build-status to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxhf-xq6v-c8mj is resolved across your whole dependency graph.

How do I detect GHSA-xxhf-xq6v-c8mj in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:embeddable-build-status, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-xxhf-xq6v-c8mj if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-xxhf-xq6v-c8mj actively exploited in the wild?

No public exploit code has been indexed for GHSA-xxhf-xq6v-c8mj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xxhf-xq6v-c8mj?

GHSA-xxhf-xq6v-c8mj has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 70th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xxhf-xq6v-c8mj?

GHSA-xxhf-xq6v-c8mj is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xxhf-xq6v-c8mj published, and has it been updated?

GHSA-xxhf-xq6v-c8mj was published on June 24, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Improper authorization in Jenkins Embeddable Build Status Plugin bypasses ViewStatus permission requirementGHSA-xxhf-xq6v-c8mj

MEDIUMFix: jenkinsci/embeddable-build-status-plugin@4021487

GHSA-xxhf-xq6v-c8mj is a medium-severity (CVSS 5.3) CWE-863 vulnerability in org.jenkins-ci.plugins:embeddable-build-status. A fix is available for org.jenkins-ci.plugins:embeddable-build-status — see the affected versions and patch details below.

Also known asCVE-2022-34180

Published

Jun 24, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs70th percentile — riskier than 70% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:embeddable-build-status

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Embeddable Build Status Plugin 2.0.3 and earlier does not correctly perform the ViewStatus permission check in the HTTP endpoint it provides for "unprotected" status badge access.

This allows attackers without any permissions to obtain the build status badge icon for any attacker-specified job and/or build.

Embeddable Build Status Plugin 2.0.4 requires ViewStatus permission to obtain the build status badge icon.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:embeddable-build-status`	all versions	2.0.4`org.jenkins-ci.plugins:embeddable-build-status:2.0.4`

Affected Products

1 product · 1 configurations

Application

embeddable build statusjenkins

≤ 2.0.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:embeddable-build-status, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:embeddable-build-status to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xxhf-xq6v-c8mj is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

Embeddable Build Status Plugin 2.0.3 and earlier does not correctly perform the ViewStatus permission check in the HTTP endpoint it provides for \"unprotected\" status badge access. This allows attackers without any permissions to obtain the build status badge icon for any attacker-specified job and/or build. Embeddable Build Status Plugin 2.0.4 requires ViewStatus permission to obtain the build status badge icon.

O3 Security · Impact-Aware SCA

Is GHSA-xxhf-xq6v-c8mj in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

CWE Classification

CWE-863CWE-863

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Jun 24, 2022

Last updated

Feb 16, 2024

Identifiers

GHSA-xxhf-xq6v-c8mj

References

Advisorynvd.nist.gov · CVE 2022 34180 Webgithub.com · 402148784b3f4b029eaf47cc26ebf6b9bc636183 Webjenkins.io · 2022 06 22 Packagegithub.com · embeddable build status plugin

Related vulnerabilities

Also affects embeddable-build-status

This CVE is medium severity; 3 of 3 other CVEs affecting embeddable-build-status are rated as high or higher (top: high).

CVE-2022-34178CVE-2022-34179CVE-2022-34180

Same weakness: CWE-863

This CVE is medium severity; 5 of 5 other CVEs with CWE-863 are rated as high or higher (top: critical).

CVE-2026-114146CVE-2026-102943CVE-2026-95860CVE-2026-63198CVE-2026-88984Browse all CWE-863

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 16, 2024

Improper authorization in Jenkins Embeddable Build Status Plugin bypasses ViewStatus permission requirementGHSA-xxhf-xq6v-c8mj

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-xxhf-xq6v-c8mj in your dependencies?