How severe is CVE-2013-5573?

No CVSS score has been assigned to CVE-2013-5573 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2013-5573?

Affected package information for CVE-2013-5573 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2013-5573?

No patch has shipped for CVE-2013-5573 yet — track the jenkins jenkins advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2013-5573 across my infrastructure?

Inventory every jenkins jenkins deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2013-5573 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2013-5573?

O3 detects and blocks CVE-2013-5573 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2013-5573 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2013-5573, including 1 documented proof-of-concept exploit on Exploit-DB and 3 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 type of vulnerability is CVE-2013-5573?

CVE-2013-5573 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2013-5573?

CVE-2013-5573 affects jenkins jenkins (1 version, e.g. 1.523). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2013-5573 published, and has it been updated?

CVE-2013-5573 was published on December 31, 2013 and was last updated on June 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2013-5573

CVE-2013-5573 is a Cross-site Scripting (XSS) vulnerability in jenkins jenkins. 4 public exploit references exist, so weaponization risk is real. O3 Security detects and blocks CVE-2013-5573 exploitation at runtime via eBPF exploit-chain detection and L7 egress monitoring, even on unpatched systems.

Cross-site scripting (XSS) vulnerability in the default markup formatter in Jenkins 1.523 allows remote attackers to inject arbitrary web script or HTML via the Description field in…

Published

Dec 31, 2013

Updated

Jun 16, 2026

Affected

0 pkgs

Patched

None yet

Exploits

4 known

Description

Cross-site scripting (XSS) vulnerability in the default markup formatter in Jenkins 1.523 allows remote attackers to inject arbitrary web script or HTML via the Description field in the user configuration.

Affected Products

1 product · 1 configurations

Application

jenkinsjenkins

1 version

1.523

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-30408webappsphp

Jenkins 1.523 - Persistent HTML Code

by Christian Catalano · Dec 18, 2013

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every jenkins jenkins deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2013-5573 yet — track the jenkins jenkins advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2013-5573 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2013-5573. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2013-5573 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2013-5573 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2013-5573

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2013-5573 being exploited in your environment?