dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-11151

HIGH · 8.2 CVSS v3.1 Published 2025-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Exposure of Sensitive Information to an Unauthorized Actor, Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in Beyaz Bilgisayar Software Design Industry and Trade Ltd. Co. CityPLus allows Detect Unpublicized Web Pages. This issue affects CityPLus: before V24.29500.1.0.

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

CityPLus before version V24.29500.1.0 contains an information disclosure vulnerability that allows unauthenticated actors to discover unpublished or hidden web pages within the application. This exposes sensitive system information that should not be accessible, potentially revealing administrative interfaces, debug endpoints, or other internal resources not intended for public access.

MitigationUpgrade CityPLus to version V24.29500.1.0 or later. Additionally, conduct a security assessment to identify any exposed sensitive pages and implement proper access controls or authentication requirements for all internal endpoints.

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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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. Identify the installed CityPLus version
    Locate the version information for your CityPLus installation. This is typically found in the application header, about page, or configuration file. Common locations include the main login page footer, an admin/settings area, or version-specific configuration files within the installation directory.
    Affected if The installed version is earlier than V24.29500.1.0 (for example, V24.x versions below 29500.1.0, or any earlier release line).
  2. Check for hidden or unpublished page exposure
    Attempt to enumerate web pages on your CityPLus server that are not linked from the main navigation. Use techniques such as: (1) checking common paths like /admin, /debug, /test, /hidden, /internal; (2) reviewing sitemap or directory listing if available; (3) using web vulnerability scanners to discover unlinked endpoints.
    Affected if Unpublished, hidden, or internal pages are accessible without authentication and expose sensitive system information.
  3. Verify administrative interface accessibility
    Attempt to access known administrative paths (such as /admin, /administrator, /manage, /backend) without providing credentials. Check if these interfaces are reachable and display administrative functionality or system configuration details.
    Affected if Administrative interfaces or dashboards are accessible to unauthenticated users.
  4. Inspect for exposed debug or diagnostic endpoints
    Probe the application for common debug and diagnostic endpoints (such as /debug, /diag, /status, /health, /info, /actuator, or similar paths). Determine if these endpoints return sensitive system information, stack traces, configuration details, or internal application state.
    Affected if Debug endpoints, diagnostic pages, or information-leaking routes are accessible without authentication.

You are affected if your CityPLus version is earlier than V24.29500.1.0 AND any unpublished pages, administrative interfaces, or debug endpoints are accessible without 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

Upgrade CityPLus to version V24.29500.1.0 or later. Additionally, conduct a security assessment to identify any exposed sensitive pages and implement proper access controls or authentication requirements for all internal endpoints.

Recommended fix Moderate confidence

V24.29500.1.0

  1. 1. Identify the current installed version of CityPLus software
  2. 2. Back up the current system configuration and data
  3. 3. Obtain the updated version V24.29500.1.0 from the vendor (Beyaz Bilgisayar Software Design Industry and Trade Ltd. Co.)
  4. 4. Apply the upgrade following the vendor's documented upgrade procedure
  5. 5. Verify the installation completed successfully
  6. 6. Test that unpublished web pages are no longer accessible to unauthorized actors
  7. 7. Confirm the version information reflects V24.29500.1.0 or later

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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