CVE-2026-30281
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 · uneditedAn arbitrary file overwrite vulnerability in MaruNuri LLC v2.0.23 allows attackers to overwrite critical internal files via the file import process, leading to arbitrary code execution or information exposure.
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 confidenceArbitrary file overwrite vulnerability in MaruNuri LLC v2.0.23 file import functionality allows unauthenticated attackers to write to arbitrary file system locations, enabling code execution via overwriting executable files or sensitive configuration files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.23CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Maru Neo.maru versionCheck the application version via its about dialog, help menu, or version file in the installation directory. Common locations: help > about, or check a version.info, version.txt, or manifest file in the program files folder.Affected if Installed version equals exactly 2.0.23
-
Locate the file import moduleNavigate the application menus to find the file import feature. Look for options labeled Import, File Import, Load Data, or similar in the main menu, toolbar, or settings panel.Affected if File import functionality exists and is accessible in the UI or via API endpoint
-
Verify if file import accepts file pathsAttempt to use the file import feature and observe if it prompts for or accepts a file path/URL input. Check if the import dialog allows specifying arbitrary file locations or uses a fixed directory.Affected if The import feature accepts user-supplied file paths or URLs without strict path validation
-
Test for path traversal vulnerabilityDuring file import, attempt to specify a path such as ../../internal/config or similar path traversal sequence to write outside the intended upload directory. Observe if the application allows writing to non-designated directories.Affected if The application permits writing files to paths outside the designated import directory using traversal sequences
-
Check application logs for write attemptsReview application logs, audit trails, or security event logs for any file write operations that targeted unexpected paths or revealed path traversal attempts.Affected if Logs show file write operations to paths outside the expected import directory
User is affected if Maru Neo.maru version 2.0.23 is installed AND the file import feature is accessible, as this combination allows arbitrary file overwrite via path traversal.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict path validation and sanitization on the file import function to restrict write operations to allowed directories only; implement file type allowlisting and enforce authentication on import endpoints.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30281 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30281 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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