# CVE-2025-1714: Username Enumeration in Gliffy

> Attackers can enumerate valid user emails and potentially cause denial of service due to lack of rate limiting in the sign-up workflow.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2025
- **Updated:** 7 Mar 2025
- **Also known as:** GHSA-4mg2-h6wh-4hj2

## What is CVE-2025-1714?

CVE-2025-1714 is a medium-severity vulnerability in Perforce Gliffy, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Lack of Rate Limiting in Sign-up workflow in Perforce Gliffy prior to version 4.14.0-7 on Gliffy online allows attacker to enumerate valid user emails and potentially DOS the server

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-1714?


## How do I fix CVE-2025-1714?

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

## Is CVE-2025-1714 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1714 and fix it if it is affected.

What it is: CVE-2025-1714 is a medium-severity vulnerability in Perforce Gliffy, published on 5 Mar 2025. 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-2025-1714 in the wild and no public exploit code.

Affected product: Perforce Gliffy. 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-2025-1714/ (Markdown: https://insights.sbomify.com/CVE-2025-1714/index.md)
```

## Sources

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

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