dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-10254

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
A flaw has been found in SourceCodester Pet Grooming Management Software 1.0. Affected is an unknown function of the file /admin/. This manipulation causes file and directory information exposure. The attack can be initiated remotely. The exploit has been published and may be used.

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

SourceCodester Pet Grooming Management Software 1.0 contains an information disclosure vulnerability in the /admin/ directory that exposes file and directory structure information. The specific vulnerable function is not identified in available documentation. This vulnerability is remotely exploitable and may allow attackers to gather reconnaissance information about the application structure.

MitigationImplement proper access controls and disable directory listing on the web server configuration for the /admin/ path. Review and secure the unknown vulnerable function to prevent unauthorized disclosure of file system information.

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

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

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. Confirm Pet Grooming Management Software installation
    Identify if SourceCodester Pet Grooming Management Software 1.0 is deployed on the server by checking for known files such as index.php in the root directory, or by reviewing application startup pages for the product name and version string.
    Affected if The software is installed and running.
  2. Test /admin/ path accessibility
    Send an HTTP GET request to http://[target]/admin/ and examine the response. Look for a directory listing that displays file names, directory contents, or a default web server index page.
    Affected if The /admin/ directory is accessible and returns a directory listing showing file or folder names.
  3. Verify directory listing is enabled
    Inspect the HTTP response body for patterns such as 'Index of /admin/', 'Directory listing for', file extension lists (e.g., .php, .txt, .config), or parent directory links (..). This indicates directory indexing is active.
    Affected if The response displays a list of files or directories within /admin/ rather than redirecting to a login page or returning a 403 error.
  4. Check web server directory listing configuration
    For Apache: examine .htaccess files in the /admin/ directory or parent directories for 'Options +Indexes' or absence of 'Options -Indexes'. For IIS: review web.config files for directoryListing enabled attribute.
    Affected if Directory listing is explicitly enabled in the web server configuration or not explicitly disabled.
  5. Confirm authentication is required for /admin/
    Attempt to access known sensitive files within /admin/ (e.g., /admin/config.php, /admin/functions.php) without credentials. Check if the server returns a login form, redirects to an authentication page, or returns HTTP 401/403 without proper session cookies.
    Affected if The /admin/ directory or its contents are accessible without any authentication challenge.

A user is affected if the /admin/ directory of Pet Grooming Management Software 1.0 is publicly accessible and displays a directory listing without requiring authentication.

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

Implement proper access controls and disable directory listing on the web server configuration for the /admin/ path. Review and secure the unknown vulnerable function to prevent unauthorized disclosure of file system information.

Recommended fix Moderate confidence
  1. Disable directory listing on the web server for the /admin/ directory (e.g., in Apache add 'Options -Indexes' in .htaccess or server config).
  2. Ensure that the /admin/ area requires authentication; enforce login or HTTP Basic Auth and restrict access to trusted users.
  3. If the application provides role‑based access control, verify that all admin functions are behind proper authorization checks.
  4. Consider restricting access to /admin/ by IP address or using a VPN if feasible.
  5. Monitor for any unusual access attempts and keep the application updated if a patched version becomes available.

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 / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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