dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2025-1418

MEDIUM · 5.1 CVSS v4.0 Published 2025-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
53/100
Remediation priority · Moderate
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 low-privileged user can access information about profiles created in Proget MDM (Mobile Device Management), which contain details about allowed/prohibited functions. The profiles do not reveal any sensitive information (including their usage in connected devices).    This issue has been fixed in 2.17.5 version of Konsola Proget (server part of the MDM suite).

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

In Proget MDM (Mobile Device Management), a low-privileged user can access information about MDM profiles containing details about allowed and prohibited functions. While the description states no sensitive information (such as device usage) is exposed, this still constitutes an unauthorized information disclosure due to improper access control on profile data.

MitigationUpgrade Konsola Proget to version 2.17.5 or later to remediate this vulnerability.

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
Adjacent
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/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 the installed Konsola Proget version
    Locate the Proget MDM installation and retrieve its version number (typically found in the application metadata, about page, or installation directory)
    Affected if version is lower than 2.17.5 (any version prior to the fix)
  2. Confirm MDM module is active
    Verify that the MDM (Mobile Device Management) functionality is enabled and in use within the Proget installation
    Affected if MDM profiles or MDM functionality is configured and active
  3. Check user role configuration
    Review the user roles and permissions defined in the Proget system, specifically looking for low-privileged or non-admin user accounts
    Affected if low-privileged user accounts exist in the system
  4. Test access to MDM profile data
    Using a low-privileged user account (non-admin), attempt to access or query MDM profile information through the Proget API or web interface
    Affected if low-privileged users can view MDM profile details containing allowed/prohibited function information

You are affected if running Konsola Proget version below 2.17.5 with MDM functionality enabled, where low-privileged users can access MDM profile information.

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 Konsola Proget to version 2.17.5 or later to remediate this vulnerability.

Recommended fix High confidence

Konsola Proget 2.17.5

  1. 1. Identify the current version of Konsola Proget MDM server currently deployed
  2. 2. Plan the upgrade to Konsola Proget version 2.17.5 or later
  3. 3. Perform the upgrade following standard deployment procedures
  4. 4. After upgrade, verify that low-privileged users can no longer access MDM profile information
  5. 5. Confirm the version has been updated to 2.17.5 or newer

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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