dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-55417

MEDIUM · 6.9 CVSS v4.0 Published 2026-07-07
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 6 weeks old

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
Chevereto is a self-hosted media-sharing platform. Starting in version 3.7.5 and prior to version 4.5.4, when a user enables the private profile option, visiting their profile HTML route (`/username`) correctly returns 404. However, the `/json` AJAX listing endpoint does not apply the same check. An unauthenticated caller who knows the target's user ID can retrieve all of that user's publicly-scoped images, revealing the username (which should be private). This is patched in Chevereto v4.5.4. No known workarounds are available.

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

Chevereto versions 3.7.5 through 4.5.3 have an information disclosure vulnerability where the `/json` AJAX listing endpoint does not enforce the private profile setting that the HTML route (`/username`) correctly applies. An unauthenticated attacker with knowledge of a target's user ID can retrieve publicly-scoped images, exposing the username that should remain private.

MitigationUpgrade to Chevereto v4.5.4 or later. No workarounds exist; the private profile check must be added to the JSON endpoint.

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:N/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 Chevereto installation and version
    Access the admin dashboard or check for a version file in the application root (commonly version.php or similar). Compare the installed version against the affected range 3.7.5 through 4.5.3.
    Affected if Installed version falls within 3.7.5 to 4.5.3 inclusive
  2. Determine if private profiles are configured
    Log into the Chevereto admin panel and navigate to user settings or profile privacy settings. Check whether any user accounts have enabled the 'private profile' or 'hide username' option.
    Affected if At least one user account has private profile settings enabled
  3. Verify the HTML endpoint enforces privacy
    Visit the public profile page for a user with private profile enabled (format: /username). Observe whether the username is hidden, obscured, or the page indicates the profile is private.
    Affected if The /username route properly hides or restricts the private user's information
  4. Test the JSON endpoint for information disclosure
    Make an unauthenticated HTTP request to the /json AJAX endpoint, providing a target user's ID (for example: /json/users/USER_ID/images or similar endpoint structure). Compare the response to what /username shows.
    Affected if The /json endpoint returns publicly-scoped images or user information that reveals the username which should be private according to the user's profile settings

If Chevereto version 3.7.5-4.5.3 is running, a user has private profiles enabled, and the /json endpoint exposes data that the /username route correctly protects, the environment is affected by this CVE.

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 to Chevereto v4.5.4 or later. No workarounds exist; the private profile check must be added to the JSON endpoint.

Recommended fix High confidence

Chevereto v4.5.4

  1. 1. Back up your Chevereto installation and database before proceeding.
  2. 2. Log in to the Chevereto admin panel as an administrator.
  3. 3. Navigate to Settings > System > Check for updates (or use the built‑in update mechanism).
  4. 4. Upgrade to version 4.5.4 (or download the release from the official Chevereto website and replace the files).
  5. 5. Verify that the version displayed in the admin dashboard shows 4.5.4.
  6. 6. Confirm that the /json endpoint now correctly respects the private profile setting.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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