dbcve.org
Jaba XpressApplication · Jaba

CVE-2018-17058

HIGH · 8.8 CVSS v3.1 Published 2020-03-02
Fix available
A fix is available. Upgrade to after 2018-09-14 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 JABA XPress Online Shop through 2018-09-14. It contains an arbitrary file upload vulnerability in the picture-upload feature of ProductEdit.aspx. An authenticated attacker may bypass the frontend filename validation and upload an arbitrary file via FileUploader.aspx.cs in FileUploader.aspx by using empty w and h parameters. This file may contain arbitrary aspx code that may be executed by accessing /Jec/ProductImages/<number>/<filename>. Accessing the file once uploaded does not require authentication.

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

JABA XPress Online Shop contains an arbitrary file upload vulnerability where an authenticated attacker bypasses frontend filename validation in FileUploader.aspx by submitting empty w and h parameters, allowing upload of malicious ASPX files that execute when accessed via /Jec/ProductImages/ without authentication.

MitigationImplement strict server-side file type validation, block executable extensions in the upload directory, disable script execution permissions on /Jec/ProductImages/, and add authentication checks for file access.

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
Jaba XpressApplication
Affected:<= 2018-09-14

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

CVSS:3.1/AV:N/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. Identify JABA XPress installation and version
    Locate the application installation directory and check version information in any version file, assembly metadata, or application footer/dashboard. Compare against the affected version date of 2018-09-14.
    Affected if The installed version is dated 2018-09-14 or earlier, or version information shows a date prior to September 2018 patches.
  2. Verify FileUploader.aspx exists
    Check if the file FileUploader.aspx exists in the web application structure, typically under the /Jec/ or application root path.
    Affected if FileUploader.aspx is present in the application, indicating the vulnerable upload component exists.
  3. Confirm upload directory is web-accessible
    Verify that the /Jec/ProductImages/ directory exists and is accessible via HTTP/HTTPS on the web server.
    Affected if The ProductImages directory is reachable over the web, meaning uploaded files can be served to users.
  4. Check for empty parameter upload bypass
    If testing is authorized, attempt an authenticated upload to FileUploader.aspx with empty w and h parameters to confirm the validation bypass is possible.
    Affected if The upload endpoint accepts files when w and h parameters are submitted empty, confirming the vulnerability condition.
  5. Verify script execution is enabled on upload directory
    Examine the web server configuration (IIS handler mappings, web.config, or directory permissions) for the /Jec/ProductImages/ directory to confirm ASPX or other script execution is permitted.
    Affected if Script execution permissions are enabled on the ProductImages directory, allowing uploaded ASPX files to execute when accessed.

A user is affected if the JABA XPress version is from before the September 2018 patch, FileUploader.aspx exists, the ProductImages directory is web-accessible, and script execution is allowed on that directory.

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
Upgrade available Upgrade to a release after 2018-09-14
Interim mitigation

Implement strict server-side file type validation, block executable extensions in the upload directory, disable script execution permissions on /Jec/ProductImages/, and add authentication checks for file access.

Fix this in Jaba Xpress Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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