dbcve.org
Path TraversalWeakness · CWE-22

CVE-2023-7309

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A path traversal vulnerability exists in the Dahua Smart Park Integrated Management Platform (also referred to as the Dahua Smart Campus Integrated Management Platform), affecting the SOAP-based GIS bitmap upload interface. The flaw allows unauthenticated remote attackers to upload arbitrary files to the server via crafted SOAP requests, including executable JSP payloads. Successful exploitation may lead to remote code execution (RCE) and full compromise of the affected system. The vulnerability is presumed to affect builds released prior to September 2023 and is said to be remediated in newer versions of the product, though the exact affected range remains undefined. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-02-15 UTC.

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

A path traversal vulnerability in the SOAP-based GIS bitmap upload interface of Dahua Smart Park/Smart Campus Integrated Management Platform allows unauthenticated attackers to upload arbitrary files, including executable JSP payloads, leading to remote code execution.

MitigationUpdate to versions released after September 2023 or apply vendor-provided patches; if immediate patching is not possible, restrict network access to the SOAP interface and monitor for indicators of compromise.

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
Network
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Dahua Smart Park/Smart Campus platform is running
    Review network-exposed services or web applications hosted on the server. Look for the Dahua web interface or administrative portals on common ports (80, 443, 8080). Check running processes or installed software listings for 'Dahua' or 'Smart Park' or 'Smart Campus' binaries or services.
    Affected if The platform is present and running on the system
  2. Determine the installed platform version
    Access the Dahua administrative web interface (if accessible) and navigate to System > About or System > Version information page. Alternatively, check installation directories for version files or consult the software inventory if managed centrally.
    Affected if The installed version predates the September 2023 updates or cannot be determined (treat as potentially affected)
  3. Verify if SOAP-based GIS bitmap upload interface is exposed
    Probe for the SOAP GIS upload endpoint. Typical paths may include /soap/gis/upload or similar URL patterns under the web root. Use a web crawler or check the application's URL structure for endpoints related to 'GIS', 'bitmap', 'upload', or 'SOAP'. Check network firewall rules to see if the web interface is externally accessible.
    Affected if The SOAP GIS bitmap upload endpoint is reachable over the network (especially from untrusted networks)
  4. Inspect web server access logs for upload-related requests
    Review web server (IIS, Apache, Tomcat) access logs for POST requests targeting the GIS upload endpoint. Look for patterns with 'upload', 'bitmap', 'gis', or 'soap' in the path. Also check for .jsp file extensions in upload request bodies or responses.
    Affected if Unauthenticated POST requests to the upload interface are logged, or unusual file upload patterns are present

A system is affected if it runs a Dahua Smart Park/Smart Campus platform version prior to the September 2023 updates and has the SOAP-based GIS bitmap upload interface network-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

Update to versions released after September 2023 or apply vendor-provided patches; if immediate patching is not possible, restrict network access to the SOAP interface and monitor for indicators of compromise.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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