How severe is CVE-2013-1933?

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

Which packages are affected by CVE-2013-1933?

CVE-2013-1933 affects the following packages: karteek-docsplit (RubyGems). Ecosystems affected: RubyGems.

How do I fix CVE-2013-1933?

The records we use list no patched version of karteek-docsplit for CVE-2013-1933. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2013-1933 in my RubyGems dependencies?

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

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

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

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

No public exploit code has been indexed for CVE-2013-1933 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 CVE-2013-1933?

CVE-2013-1933 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 79th 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-2013-1933?

CVE-2013-1933 is classified as OS Command Injection (CWE-78). 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-2013-1933 published, and has it been updated?

CVE-2013-1933 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

💎 RubyGems

Not in CISA KEV

CVE-2013-1933 — karteek-docsplit

CVE-2013-1933 is a OS Command Injection vulnerability in karteek-docsplit. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Karteek Docsplit vulnerable to OS Command Injection

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

💎karteek-docsplit

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

Description

The extract_from_ocr function in lib/docsplit/text_extractor.rb in the Karteek Docsplit (karteek-docsplit) gem 0.5.4 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a PDF filename.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
💎RubyGems	`karteek-docsplit`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

karteek-docsplitdocumentcloud

1 version

0.5.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for karteek-docsplit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of karteek-docsplit for CVE-2013-1933. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

The `extract_from_ocr` function in `lib/docsplit/text_extractor.rb` in the Karteek Docsplit (karteek-docsplit) gem 0.5.4 for Ruby allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a PDF filename.