dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-28267

MEDIUM · 5.5 CVSS v3.0 Published 2026-03-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
Multiple i-フィルター products are configured with improper file access permission settings. Files may be created or overwritten in the system directory or backup directory by a non-administrative user.

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

Multiple i-フィルター (i-filter) products have improper file access permission configurations that allow non-administrative users to create or overwrite files in system directories or backup directories. This local privilege escalation vector could enable an attacker to overwrite system files or executables, potentially leading to arbitrary code execution or system compromise.

MitigationRestrict write access permissions on system directories and backup directories to administrator accounts only, following the principle of least privilege. Verify that non-administrative users cannot modify files in protected system locations.

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

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 if i-filter product is installed
    Check for i-フィルター or i-filter installation by searching common installation paths (C:\Program Files\i-filter, C:\Program Files (x86)\i-filter) or checking Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for i-filter entries
    Affected if i-filter software is present on the system
  2. Locate i-filter installation directory
    Find the main installation directory by checking the registry key identified in step 1, or using 'dir /s /b C:\*ifilter*' or 'dir /s /b C:\*i-フィルター*' to search for i-filter related folders
    Affected if Installation directory is found on the system
  3. Identify system directories used by i-filter
    Examine the i-filter installation directory for subdirectories such as 'system', 'sys', 'backup', 'backupdir', or similar names that may contain system files or backup data
    Affected if System or backup subdirectories exist within the i-filter installation folder
  4. Check file permissions on system directories
    Right-click the identified system directories, select Properties, then Security tab. Review the permissions for Users or non-administrative groups. Alternatively, run 'icacls [directory_path]' from command prompt to list effective permissions
    Affected if Users group or non-administrative accounts are granted Write or Full Control permissions on system directories
  5. Check file permissions on backup directories
    Right-click backup directories within the i-filter installation, select Properties, then Security tab. Review permissions for standard user accounts. Alternatively, run 'icacls [backup_directory_path]' to view permission entries
    Affected if Users group or non-administrative accounts are granted Write or Create permissions on backup directories
  6. Verify write access with limited account
    If a non-administrative test account is available, attempt to create a test file in the identified system or backup directories using 'echo test > [directory_path]\test.txt' as that limited user
    Affected if Non-administrative user successfully creates or modifies files in system or backup directories

A user is affected if non-administrative accounts have Write or Create permissions on i-filter's system directories or backup directories, allowing potential privilege escalation through file overwrite.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict write access permissions on system directories and backup directories to administrator accounts only, following the principle of least privilege. Verify that non-administrative users cannot modify files in protected system locations.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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