dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-7519

HIGH · 7.3 CVSS v3.1 Published 2026-05-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 vulnerability has been found in Fujian Apex LiveBOS up to 2.0. Impacted is an unknown function of the file /feed/UploadImage.do of the component Endpoint. Such manipulation of the argument filename leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 2.1 is recommended to address this issue. Upgrading the affected component is advised.

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 exists in the /feed/UploadImage.do endpoint of Fujian Apex LiveBOS up to version 2.0. The filename parameter is not properly validated, allowing attackers to manipulate it to write files to arbitrary directories on the server through directory traversal sequences (e.g., ../../../). This is a remote, high-severity vulnerability exploitable without authentication.

MitigationUpgrade Fujian Apex LiveBOS to version 2.1 to remediate this vulnerability. If immediate upgrade is not possible, consider restricting access to the /feed/UploadImage.do endpoint via network-level controls until the upgrade can be performed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 the installed LiveBOS version
    Check the application's version information through the web interface, API endpoint, or configuration files. Look for version display in the login page, about page, or server configuration.
    Affected if The installed version is Fujian Apex LiveBOS 2.0 or lower.
  2. Verify the /feed/UploadImage.do endpoint exists
    Send an HTTP request to your server at the path /feed/UploadImage.do (e.g., using curl or a browser). Check if the endpoint responds or returns any application-specific response.
    Affected if The endpoint is accessible and returns a valid application response, indicating the upload functionality is present.
  3. Test for directory traversal in the filename parameter
    Send a POST request to /feed/UploadImage.do with a filename parameter containing traversal sequences such as ../../../test.txt. Observe if the application accepts the path or if it rejects the traversal sequence.
    Affected if The application accepts directory traversal sequences in the filename parameter without proper sanitization, allowing path manipulation.

If Fujian Apex LiveBOS version 2.0 or earlier is running and the /feed/UploadImage.do endpoint accepts directory traversal sequences in the filename parameter, the environment is affected by CVE-2026-7519.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Fujian Apex LiveBOS to version 2.1 to remediate this vulnerability. If immediate upgrade is not possible, consider restricting access to the /feed/UploadImage.do endpoint via network-level controls until the upgrade can be performed.

Recommended fix High confidence

Fujian Apex LiveBOS 2.1

  1. 1. Identify the current version of Fujian Apex LiveBOS by checking the application or consulting system documentation
  2. 2. Perform a complete backup of the current Fujian Apex LiveBOS installation including database and configuration files
  3. 3. Obtain the official Fujian Apex LiveBOS version 2.1 from the vendor's official distribution channels
  4. 4. Follow the vendor's official upgrade procedure documentation to apply version 2.1
  5. 5. After upgrade, verify that the /feed/UploadImage.do endpoint now properly sanitizes the filename parameter and does not allow path traversal
  6. 6. Test that the image upload functionality works correctly in the updated version
Caveat Review vendor release notes for version 2.1 to check for any breaking changes or migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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