# CVE-2021-25002: Tipsacarrier < 1.5.0.5 - Unauthenticated Orders Disclosure

> Unauthenticated attackers can access order data including client addresses and phone numbers due to missing authorization checks in the Tipsacarrier plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-697f-3w53-jxc5

## What is CVE-2021-25002?

CVE-2021-25002 is a high-severity missing authorization vulnerability in Unknown Tipsacarrier, published on 2 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Tipsacarrier WordPress plugin before 1.5.0.5 does not have any authorisation check in place some functions, which could allow unauthenticated users to access Orders data which could be used to retrieve the client full address, name and phone via tracking URL

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2021-25002?

It affects 1 product.


Products: Tipsacarrier Project Tipsacarrier.

## How do I fix CVE-2021-25002?

No fix has been published for CVE-2021-25002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-25002 being exploited?

There is no known exploitation of CVE-2021-25002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25002 and fix it if it is affected.

What it is: CVE-2021-25002 is a high-severity missing authorization vulnerability in Unknown Tipsacarrier, published on 2 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25002 in the wild and no public exploit code.

Affected product: Unknown Tipsacarrier. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-25002/ (Markdown: https://insights.sbomify.com/CVE-2021-25002/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-25002
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-25002
- OSV: https://osv.dev/vulnerability/CVE-2021-25002

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-25002/
Summaries are generated and may contain mistakes; the official description above is the record.