Skip to content
Fencer Intel
medium 4.3

CVE-2013-0328 json

Jenkins subject to Cross-site Scripting

published 2013-03-19 13 y ago modified 2026-06-16 4 mo ago also GHSA-q5f8-fxrx-pw6f , EUVD-2022-4894

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

Cross-site scripting (XSS) vulnerability in Jenkins before 1.502 and LTS before 1.480.3 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors.

Patch / fix

  • maven org.jenkins-ci.main:jenkins-core 1.502
  • jenkins openshift 1 1.502-1.el6op
  • rubygem-rack openshift 1 1:1.3.0-4.el6op
  • ruby193-rubygem-rack openshift 1 1:1.4.1-4.el6
  • openshift-origin-cartridge-jenkins-1.4 openshift 1 1.0.3-1.el6op

red hat advisories RHSA-2013:0638

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-0328 updated cvss 4.3

jenkins: XSS

  • Red Hat OpenShift Enterprise Infrastructure rubygem-rack 1.3.0-4.el6op, ruby193-rubygem-rack 1.4.1-4.el6 Red Hat OpenShift Enterprise Node jenkins 1.502-1.el6op, rubygem-rack 1.3.0-4.el6op, ruby193-rubygem-rack 1.4.1-4.el6, openshift-origin-cartridge-jenkins-1.4 1.0.3-1.el6op
    fixed: vendor fix RHSA-2013:0638

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.30% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.jenkins-ci.main:jenkins-core
<1.502
1.502

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery
  • CWE-79 Improper Neutralization of Input During Web Page Generation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.