dbcve.org
PingpongApplication · Harvard

CVE-2026-32097

HIGH · 8.8 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 7.27.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
PingPong is a platform for using large language models (LLMs) for teaching and learning. Prior to 7.27.2, an authenticated user may be able to retrieve or delete files outside the intended authorization scope. This issue could result in retrieval or deletion of private files, including user-uploaded files and model-generated output files. Exploitation required authentication and permission to view at least one thread for retrieval, and authentication and permission to participate in at least one thread for deletion. This vulnerability is fixed in 7.27.2.

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 · high confidence

PingPong platform prior to 7.27.2 contains a broken access control vulnerability allowing authenticated users with basic thread access to retrieve or delete files outside their intended authorization scope. This could enable unauthorized access to or deletion of private user-uploaded files and model-generated output files through improper path validation or insufficient permission checks.

MitigationUpgrade to PingPong version 7.27.2 or later to obtain the patched code that implements proper file access authorization checks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PingpongApplication
Affected:< 7.27.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Check installed PingPong version
    Locate the PingPong application version number in the product UI (typically in About or Settings), or query the API endpoint that returns version information, or check the installation manifest file if accessible
    Affected if The installed version is lower than 7.27.2
  2. Verify user role permissions
    Review user account roles and permissions configuration to determine if any user accounts possess either 'thread-view' or 'thread-participation' permissions
    Affected if Any user account has thread-view or thread-participation permissions enabled
  3. Confirm file operation endpoints are exposed
    Check the PingPong web interface or API documentation for file retrieval or deletion endpoints that accept path parameters; test accessing file operation features with a valid authenticated session
    Affected if File operation endpoints accepting path parameters are accessible to authenticated users with the relevant permissions
  4. Test path traversal in file parameters
    Using an authenticated session with thread-view or thread-participation permissions, attempt to access files outside the intended directory by manipulating path parameters (e.g., ../../) in file operation requests
    Affected if The application allows path traversal and returns files from directories outside the user's authorized scope

The environment is affected if PingPong version is below 7.27.2 AND users with thread-view or thread-participation permissions can access file operations via path parameters that are not properly validated.

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
Upgrade available Upgrade to 7.27.2 or later
Fixed in 7.27.2
Interim mitigation

Upgrade to PingPong version 7.27.2 or later to obtain the patched code that implements proper file access authorization checks.

Recommended fix High confidence

7.27.2

  1. Identify the currently installed PingPong version by checking the application settings or deployment configuration
  2. Review PingPong's official upgrade documentation for your deployment method (e.g., package manager, Docker, manual installation)
  3. Upgrade PingPong to version 7.27.2 or later following the standard upgrade procedure
  4. Verify the upgrade was successful by checking the installed version
  5. Test that the authorization controls now properly restrict file access to authorized threads only

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

Fix this in Pingpong Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32097 — 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-2026-32097 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