dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-1714

MEDIUM · 6.9 CVSS v4.0 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Perforce Gliffy prior to version 4.14.0-7 lacks rate limiting on the sign-up endpoint, allowing attackers to repeatedly submit registration requests to enumerate valid user emails (by observing which emails return 'already registered' responses) and potentially cause denial of service by flooding the endpoint.

MitigationUpgrade Perforce Gliffy to version 4.14.0-7 or later, which includes rate limiting fixes. Additionally, implement rate limiting on authentication-related endpoints as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Perforce Gliffy version
    Access the Gliffy administration console or check the software release notes/built-in version information typically found in Help > About or the application's footer. Alternatively, query the application's API endpoint that returns version metadata if available.
    Affected if The installed version is earlier than 4.14.0-7 (e.g., 4.14.0-6, 4.13.x, or earlier).
  2. Locate the sign-up or registration endpoint configuration
    Examine the web server configuration files (such as nginx.conf, httpd.conf, or the application-specific configuration) to identify how the /signup, /register, or /registration endpoint is defined and whether it has rate limiting directives applied.
    Affected if Rate limiting rules (such as limit_req in nginx, RateLimit directives in Apache, or application-level throttling) are absent or not configured for the sign-up endpoint.
  3. Review authentication-related logs for repeated registration attempts
    Access the application logs or web server access logs and search for patterns of consecutive POST requests to the sign-up endpoint originating from the same IP address within a short time window.
    Affected if Logs show numerous registration requests from a single source without being blocked or throttled, or if logs indicate 'already registered' responses being returned repeatedly to the same IP.
  4. Test the sign-up endpoint response behavior
    Submit two registration requests with the same email address to the live sign-up endpoint and observe the response message. Then submit requests with different emails and compare the response timing and content.
    Affected if The endpoint returns an explicit 'email already registered' or 'user exists' message rather than a generic error, or if response times do not increase after multiple failed attempts (indicating no throttling).

The environment is affected if Perforce Gliffy version is earlier than 4.14.0-7 AND the sign-up endpoint lacks rate limiting configuration, allowing repeated registration requests to be processed without restriction.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Perforce Gliffy to version 4.14.0-7 or later, which includes rate limiting fixes. Additionally, implement rate limiting on authentication-related endpoints as a defense-in-depth measure.

Recommended fix Moderate confidence

4.14.0-7

  1. Identify the current version of Perforce Gliffy deployed in your environment
  2. Access the Perforce support portal or admin console to obtain the upgrade package for version 4.14.0-7 or later
  3. Review upgrade documentation and release notes for any prerequisites
  4. Perform a backup of the current Gliffy installation and associated data
  5. Execute the upgrade following the documented upgrade procedure
  6. Verify the upgrade was successful by checking the version number
  7. Test the sign-up workflow to confirm rate limiting is functioning properly
  8. Monitor logs for any unusual sign-up activity that might indicate exploitation attempts

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-1714 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-1714 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data