How severe is GHSA-784j-h234-m56x?

GHSA-784j-h234-m56x has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-784j-h234-m56x?

GHSA-784j-h234-m56x affects the following packages: org.jenkins-ci.plugins:script-security (Maven). Ecosystems affected: Maven.

How do I fix GHSA-784j-h234-m56x?

Update org.jenkins-ci.plugins:script-security to 1.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-784j-h234-m56x is resolved across your whole dependency graph.

How do I detect GHSA-784j-h234-m56x in my Maven dependencies?

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

How do I mitigate GHSA-784j-h234-m56x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-784j-h234-m56x actively exploited in the wild?

Yes. There are 14 known exploit references for GHSA-784j-h234-m56x, including 3 documented proof-of-concept exploits on Exploit-DB and 8 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-784j-h234-m56x?

GHSA-784j-h234-m56x has an EPSS (Exploit Prediction Scoring System) score of 98.4%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for GHSA-784j-h234-m56x?

A Nuclei detection template exists for GHSA-784j-h234-m56x, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-784j-h234-m56x published, and has it been updated?

GHSA-784j-h234-m56x was published on May 13, 2022 and was last updated on February 20, 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

HIGH severity

Protection Mechanism Failure in Jenkins Script Security PluginGHSA-784j-h234-m56x

HIGHFix: jenkinsci/script-security-plugin@2c5122e

GHSA-784j-h234-m56x is a high-severity (CVSS 8.8) remote code execution vulnerability in org.jenkins-ci.plugins:script-security. 14 public exploit references exist, so weaponization risk is real. A fix is available for org.jenkins-ci.plugins:script-security — see the affected versions and patch details below.

Also known asCVE-2019-1003000

Published

May 13, 2022

Updated

Feb 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

14 known

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

EPSS Exploitation Probability

via FIRST.org ↗

98.4%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-784j-h234-m56x by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:script-security

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

A sandbox bypass vulnerability exists in Script Security Plugin 1.49 and earlier in src/main/java/org/jenkinsci/plugins/scriptsecurity/sandbox/groovy/GroovySandbox.java that allows attackers with the ability to provide sandboxed scripts to execute arbitrary code on the Jenkins master JVM.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:script-security`	all versions	1.50`org.jenkins-ci.plugins:script-security:1.50`

Affected Products

2 products · 2 configurations

Application

script securityjenkins

≤ 1.49

range

Application

openshift container platformredhat

1 version

3.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46453webappsjava

Jenkins Plugin Script Security 1.49/Declarative 1.3.4/Groovy 2.60 - Remote Code Execution

by wetw0rk · Feb 25, 2019

Exploit-DB Source

EDB-46572remotejava✓ Verified

Jenkins 2.137 and Pipeline Groovy Plugin 2.61 - ACL Bypass and Metaprogramming Remote Code Execution (Metasploit)

by Metasploit · Mar 19, 2019

Exploit-DB Source

EDB-46427webappsjava✓ Verified

Jenkins Plugin Script Security < 1.50/Declarative < 1.3.4.1/Groovy < 2.61.1 - Remote Code Execution (PoC)

by orange · Feb 19, 2019

Exploit-DB Source

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:script-security, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:script-security to 1.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-784j-h234-m56x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How to detect GHSA-784j-h234-m56x

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-784j-h234-m56x -u https://target

Template: Jenkins Script Security Plugin <=1.49 - Sandbox Bypass
Severity: high
Impact: Attackers with permission to submit sandboxed scripts can bypass sandbox protections and execute arbitrary code on the Jenkins master JVM, potentially compromising the entire Jenkins environment and all managed systems.
Remediation: Upgrade to Jenkins Script Security Plugin version 1.50 or later.

Template by ProjectDiscovery nuclei-templates (sttlr), MIT licensed. View the full template. Scan only systems you are authorised to test.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.11	`atomic-enterprise-service-catalog-1:3.11.82-1.git.1673.133961e.el7`	RHBA-2019:0326

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-784j-h234-m56x in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

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

Weaponization

Timeline

First exploit

Feb 25, 2019

Disclosed

May 13, 2022

Last updated

Feb 20, 2024

Identifiers

GHSA-784j-h234-m56x

References

Advisorynvd.nist.gov Webgithub.com Webaccess.redhat.com Webaccess.redhat.com Webjenkins.io Webexploit-db.com Webexploit-db.com Webpacketstormsecurity.com Webrapid7.com

Related vulnerabilities

This CVE is high severity; 6 of 8 other CVEs affecting script-security are rated as high or higher (top: high).

CVE-2026-57280CVE-2026-57281CVE-2026-42519CVE-2024-52549CVE-2024-34145CVE-2024-34144CVE-2023-24422CVE-2022-45379

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 20, 2024

Protection Mechanism Failure in Jenkins Script Security PluginGHSA-784j-h234-m56x

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

How to detect GHSA-784j-h234-m56x

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-784j-h234-m56x in your dependencies?