dbcve.org
Internet Reservation Module Next GenerationPlugin / extension · Resortdata

CVE-2023-39424

HIGH · 8.8 CVSS v3.1 Published 2023-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A vulnerability in RDPngFileUpload.dll, as used in the IRM Next Generation booking system, allows a remote attacker to upload arbitrary content (such as a web shell component) to the SQL database and execute it with SYSTEM privileges. This vulnerability requires authentication to be exploited but can be paired with another vulnerability in the platform (CVE-2023-39420, which grants access to hardcoded credentials) to carry the attack without having assigned credentials. 

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/file upload vulnerability in RDPngFileUpload.dll within the IRM Next Generation booking system permits authenticated remote attackers to upload arbitrary content, including web shell components, directly to the SQL database. Uploaded content executes with SYSTEM privileges. The attack can be chained with CVE-2023-39420 (hardcoded credentials) to achieve unauthenticated exploitation.

MitigationImplement strict server-side validation of file uploads (whitelist allowed extensions/content types, reject executable content), remove the arbitrary file upload capability from RDPngFileUpload.dll, and address the hardcoded credentials issue from CVE-2023-39420. Consider network segmentation to limit database execution privileges.

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
Internet Reservation Module Next GenerationPlugin / extension
Affected:= 5.3.2.15

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. Locate RDPngFileUpload.dll on the system
    Search for the file RDPngFileUpload.dll in the IRM Next Generation installation directory, typically found in the web application's bin folder or modules directory. Use file system search or inspect the deployed application structure.
    Affected if The file exists and is present in a web-accessible directory, indicating the vulnerable component is deployed.
  2. Identify installed version of Resortdata IRM Next Generation
    Check the application version by examining the DLL's file properties (right-click, Properties > Details), the application's about page, configuration files, or the Windows installed programs list. Look for version 5.3.2.15 specifically.
    Affected if The installed version is exactly 5.3.2.15, matching the affected version range.
  3. Verify file upload endpoint accessibility
    Inspect the web application's configuration (web.config, application config files) and routing definitions to identify if the RDPngFileUpload.dll upload functionality is exposed and enabled. Check for upload-related routes or handlers pointing to this DLL.
    Affected if The file upload endpoint is accessible (not disabled or restricted) and the upload functionality is enabled in the configuration.
  4. Check for hardcoded credentials (CVE-2023-39420)
    Review configuration files, DLL resources, or embedded strings within RDPngFileUpload.dll for hardcoded credentials, database connection strings, or default administrative accounts. Use a text search or binary analysis tool on the DLL.
    Affected if Hardcoded credentials or default accounts are found, which would allow unauthenticated access to chain with this vulnerability.
  5. Confirm database execution privileges
    Review the database user account used by the IRM application. Check if it has elevated privileges or execute permissions that could allow writing web shell content to be served by the web server.
    Affected if The application's database account has SYSTEM-level privileges or permissions to write to web-accessible locations.

You are affected if RDPngFileUpload.dll is present and the IRM Next Generation version is 5.3.2.15 with the file upload feature enabled and accessible.

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

Implement strict server-side validation of file uploads (whitelist allowed extensions/content types, reject executable content), remove the arbitrary file upload capability from RDPngFileUpload.dll, and address the hardcoded credentials issue from CVE-2023-39420. Consider network segmentation to limit database execution privileges.

Fix this in Internet Reservation Module Next Generation Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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