How severe is CVE-2014-2260?

CVE-2014-2260 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2014-2260?

CVE-2014-2260 affects the following packages: ajenti (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-2260?

Update ajenti to 1.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2260 is resolved across your whole dependency graph.

How do I detect CVE-2014-2260 in my PyPI dependencies?

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

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

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2014-2260 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2014-2260, including 2 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 CVE-2014-2260?

CVE-2014-2260 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th 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 CVE-2014-2260?

CVE-2014-2260 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.

When was CVE-2014-2260 published, and has it been updated?

CVE-2014-2260 was published on May 17, 2022 and was last updated on September 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

CVE-2014-2260 — ajenti

MEDIUMFix: Eugeny/ajenti@3270fd1

CVE-2014-2260 is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in ajenti. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for ajenti — see the affected versions and patch details below.

Ajenti Cross-site scripting (XSS) vulnerability

Also known asPYSEC-2014-98

Published

May 17, 2022

Updated

Sep 3, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% 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

🐍ajenti

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

Description

Cross-site scripting (XSS) vulnerability in plugins/main/content/js/ajenti.coffee in Eugene Pankov Ajenti 1.2.13 allows remote authenticated users to inject arbitrary web script or HTML via the command field in the Cron functionality.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ajenti`	all versions	1.2.15`pip install --upgrade 'ajenti==1.2.15'`

Affected Products

1 product · 1 configurations

Application

ajentiajenti

1 version

1.2.13

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.

Cross-site scripting (XSS) vulnerability in plugins/main/content/js/ajen…

github.comNVDMay 2014

Report on packetstormsecurity.com

packetstormsecurity.comNVDMay 2014

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ajenti, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ajenti to 1.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-2260 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

Cross-site scripting (XSS) vulnerability in `plugins/main/content/js/ajenti.coffee` in Ajenti before 1.2.15 allows remote authenticated users to inject arbitrary web script or HTML via the command field in the Cron functionality.

O3 Security · Impact-Aware SCA

Is CVE-2014-2260 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-79Cross-site Scripting (XSS)

Weaponization

No Nuclei template or Metasploit module yet. 2 public proof-of-concept references are listed on this page.

Timeline

First exploit

May 1, 2014

Disclosed

May 17, 2022

Last updated

Sep 3, 2024

Identifiers

CVE-2014-2260

PYSEC-2014-98

References

Advisorynvd.nist.gov · CVE 2014 2260 Webgithub.com Webgithub.com Webgithub.com · 3270fd1d78391bb847b4c9ce37cf921f485b1310 Webgithub.com · 3270fd1d78391bb847b4c9ce37cf921f485b1310 Webgithub.com · PYSEC 2014 98.yaml Webweb.archive.org Webpacketstormsecurity.com · Ajenti 1.2.13 Cross Site Scripting Packagegithub.com · ajenti

Related vulnerabilities

Also affects ajenti

This CVE is medium severity, in line with the other 2 CVEs affecting ajenti.

CVE-2014-4301CVE-2018-18548

Same weakness: CWE-79

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

CVE-2026-113787CVE-2026-44267CVE-2026-96632CVE-2026-9086CVE-2026-118246CVE-2026-118251Browse all CWE-79

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 3, 2024