How severe is CVE-2014-3242?

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

Which packages are affected by CVE-2014-3242?

CVE-2014-3242 affects the following packages: soappy (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-3242?

The records we use list no patched version of soappy for CVE-2014-3242. 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-2014-3242 in my PyPI dependencies?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

Yes. There are 1 known exploit references for CVE-2014-3242, including 1 in-the-wild exploitation 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-3242?

CVE-2014-3242 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-2014-3242?

CVE-2014-3242 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2014-3242 was published on May 17, 2022 and was last updated on July 7, 2026. 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

CVE-2014-3242 — soappy

CVE-2014-3242 is a Information Exposure vulnerability in soappy. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

SOAPpy vulnerable to XML External Entity attacks

Also known asPYSEC-2026-924

Published

May 17, 2022

Updated

Jul 7, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 31, 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

🐍soappy

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

SOAPpy 0.12.5 allows remote attackers to read arbitrary files via a SOAP request containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`soappy`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

soappymakina-corpus

1 version

0.12.5

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.

SOAPpy 0.12.5 allows remote attackers to read arbitrary files via a SOAP…

pnigos.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 soappy, 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 soappy for CVE-2014-3242. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3242 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works