dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-13982

HIGH · 8.7 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 →
96/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
SPON IP Network Broadcast System, a digital audio transmission platform developed by SPON Communications, contains an arbitrary file read vulnerability in the rj_get_token.php endpoint. The flaw arises from insufficient input validation on the jsondata[url] parameter, which allows attackers to perform directory traversal and access sensitive files on the server. An unauthenticated remote attacker can exploit this vulnerability by sending a crafted POST request to read arbitrary files, potentially exposing system configuration, credentials, or internal logic. An affected version range is undefined.

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

The SPON IP Network Broadcast System contains an arbitrary file read vulnerability in the rj_get_token.php endpoint. The jsondata[url] parameter lacks sufficient input validation, allowing directory traversal attacks. An unauthenticated remote attacker can send crafted POST requests to read arbitrary files on the server, potentially exposing sensitive system data.

MitigationImplement strict input validation and path sanitization on the jsondata[url] parameter to prevent directory traversal sequences. If available, apply vendor patches; otherwise, consider deploying a WAF rule or network segmentation to mitigate exploitation.

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:N/VA:N/SC:N/SI:N/SA:N/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. Confirm SPON IP Network Broadcast System is installed
    Identify the product by reviewing web server directories, checking application banners, or searching for SPON-related files such as 'rj_get_token.php', 'broadcast', or 'SPON' in the web root.
    Affected if The system is running SPON IP Network Broadcast System software.
  2. Locate the vulnerable rj_get_token.php endpoint
    Search the web root for the file rj_get_token.php. Common paths may include /api/, /php/, or the main web application directory. Attempt to access it via HTTP GET or check for its presence in the deployed application files.
    Affected if The file rj_get_token.php exists and is accessible via the web server.
  3. Verify the jsondata[url] parameter accepts input
    Review the source code of rj_get_token.php to confirm it processes the jsondata[url] parameter. Look for the request handling logic that extracts this parameter from POST data.
    Affected if The endpoint accepts and processes the jsondata[url] parameter without validation.
  4. Check for lack of input sanitization on jsondata[url]
    Examine the rj_get_token.php code to see if the url parameter undergoes path sanitization. Look for functions that strip or validate directory traversal sequences like '../' or '..\'. If no validation exists, the parameter is unsanitized.
    Affected if The jsondata[url] parameter does not sanitize or block directory traversal sequences.
  5. Confirm the endpoint is accessible without authentication
    Test accessing the rj_get_token.php endpoint without providing any authentication credentials. Send a crafted POST request with a test payload to verify if the server processes it.
    Affected if The rj_get_token.php endpoint can be accessed and exploited without any authentication.

A system is affected if it runs SPON IP Network Broadcast System with the rj_get_token.php endpoint accessible without authentication and the jsondata[url] parameter accepts unsanitized input susceptible to directory traversal.

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 input validation and path sanitization on the jsondata[url] parameter to prevent directory traversal sequences. If available, apply vendor patches; otherwise, consider deploying a WAF rule or network segmentation to mitigate exploitation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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