dbcve.org
Maarch RmApplication · Maarch

CVE-2019-15855

CRITICAL · 9.1 CVSS v3.1 Published 2020-01-17
Fix available
A fix is available. Upgrade to 2.5 or later.
See remediation →
100/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
An issue was discovered in Maarch RM before 2.5. A path traversal vulnerability allows an unauthenticated remote attacker to overwrite any files with a crafted POST request if the default installation procedure was followed. This results in a permanent Denial of Service.

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

A path traversal vulnerability in Maarch RM before version 2.5 allows unauthenticated remote attackers to craft POST requests that traverse directory paths and overwrite arbitrary files on the server, resulting in permanent denial of service.

MitigationUpgrade to Maarch RM version 2.5 or later which contains the patch for proper path validation. Apply web server access controls to restrict write permissions and disable unauthenticated file handling endpoints as a compensating control until upgrade is complete.

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
Maarch RmApplication
Affected:< 2.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify Maarch RM version
    Check the installed Maarch RM version by accessing the application admin interface, reading the version file in the installation directory, or querying the application about page. Common paths include version.php, info.php, or the administration dashboard.
    Affected if The installed version is any version prior to 2.5 (for example 2.0, 2.3, 2.4, etc.)
  2. Verify path traversal endpoint exposure
    Identify endpoints that handle file uploads, file storage, or document processing within the Maarch RM installation. Review the web server configuration and application routing to locate any unauthenticated file handling endpoints.
    Affected if Any endpoint handling file operations is accessible without authentication and accepts user-supplied paths in POST requests
  3. Confirm write access to application directories
    Review file system permissions on the Maarch RM web root and subdirectories. Check if the web server user has write access to directories beyond the intended upload folders.
    Affected if The web server process has write permissions to directories outside the designated upload/storage areas, allowing path traversal to overwrite system files
  4. Test for unauthenticated POST request handling
    Send a crafted POST request with path traversal sequences (such as ../../) targeting file handling endpoints to verify if the application processes the request without authentication.
    Affected if The application accepts and processes unauthenticated POST requests with path traversal patterns, allowing file writes outside the intended directory

A user is affected if their Maarch RM installation is version 2.5 or earlier and exposes any unauthenticated file handling endpoints that accept POST requests with path traversal sequences.

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
Upgrade available Upgrade to 2.5 or later
Fixed in 2.5
Interim mitigation

Upgrade to Maarch RM version 2.5 or later which contains the patch for proper path validation. Apply web server access controls to restrict write permissions and disable unauthenticated file handling endpoints as a compensating control until upgrade is complete.

Recommended fix High confidence

2.5

  1. 1. Back up the current Maarch RM installation and database before proceeding with any upgrade.
  2. 2. Download Maarch RM version 2.5 from the official Maarch repository (labs.maarch.org or official download channels).
  3. 3. Extract the new version 2.5 files to replace the existing installation.
  4. 4. Run the database migration scripts provided with version 2.5 to update the schema.
  5. 5. Verify that the web server configuration points to the new version 2.5 installation.
  6. 6. Test that the application functions correctly after the upgrade.
  7. 7. Verify the fix by attempting a path traversal request - it should be blocked by the patched version.
Caveat Limited information available; test thoroughly in a staging environment before production deployment

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

Fix this in Maarch Rm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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