dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-25203

HIGH · 7.8 CVSS v3.1 Published 2026-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Samsung MagicINFO 9 Server Incorrect Default Permissions Local Privilege Escalation Vulnerability This issue affects MagicINFO 9 Server: less than 21.1091.1.

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

Samsung MagicINFO 9 Server versions prior to 21.1091.1 contain incorrect default permissions that allow a local attacker to gain elevated privileges on the affected system. The vulnerability stems from improper permission configuration on the server application or its associated files, enabling a user with limited access to escalate to administrative or system-level privileges.

MitigationUpgrade Samsung MagicINFO 9 Server to version 21.1091.1 or later. Until patched, limit local server access to trusted personnel and audit existing user permissions on the system.

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

CVSS:3.1/AV:L/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. Locate Samsung MagicINFO 9 Server installation
    Search the file system for directories named 'MagicINFO' or 'Samsung MagicINFO', typically found under Program Files or a custom installation path on the Windows server.
    Affected if The server software is installed on the system.
  2. Identify installed version
    Locate a version file, About dialog, or executable properties (right-click the main .exe file and select Properties > Details) within the MagicINFO installation directory. Compare the version number to 21.1091.1.
    Affected if The installed version is lower than 21.1091.1.
  3. Inspect file permissions on server application directory
    Right-click the main MagicINFO installation folder, select Properties > Security tab. Review which users and groups have Full Control or Modify permissions beyond Administrators and SYSTEM.
    Affected if Non-administrator users or groups are granted Full Control or Modify permissions on the server directory.
  4. Verify permissions on configuration files
    Check individual .xml, .conf, or .ini configuration files in the MagicINFO config folder. Right-click each file, go to Properties > Security, and verify write permissions for standard users.
    Affected if Standard users or low-privilege accounts have write access to configuration files.
  5. Check service account privileges
    Open Services (services.msc), find the MagicINFO service, right-click and select Properties. Note the Log On account, then verify what permissions that account has to the application files.
    Affected if The service runs under a low-privilege account that has excessive file permissions.

A system is affected if Samsung MagicINFO 9 Server is installed with a version lower than 21.1091.1 AND non-administrator accounts have elevated permissions (Full Control or Modify) on the server application files or configuration files.

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 Samsung MagicINFO 9 Server to version 21.1091.1 or later. Until patched, limit local server access to trusted personnel and audit existing user permissions on the system.

Recommended fix Moderate confidence

21.1091.1

  1. 1. Identify the current version of Samsung MagicINFO 9 Server installed in your environment
  2. 2. Create a complete backup of the MagicINFO 9 Server installation, including all configuration files and databases
  3. 3. Download the updated MagicINFO 9 Server version 21.1091.1 or later from the official Samsung support portal
  4. 4. Stop the MagicINFO 9 Server service before applying the update
  5. 5. Install the updated version (21.1091.1 or later) following Samsung's standard upgrade procedure
  6. 6. Restart the MagicINFO 9 Server service
  7. 7. Verify the installation was successful and the service is running correctly
  8. 8. Confirm that file and directory permissions have been properly applied with the update
Caveat Review release notes for any configuration or feature changes before upgrading; test in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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