dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2019-25714

CRITICAL · 9.3 CVSS v4.0 Published 2026-04-21
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
Seeyon OA A8 contains an unauthenticated arbitrary file write vulnerability in the /seeyon/htmlofficeservlet endpoint that allows remote attackers to write arbitrary files to the web application root by sending specially crafted POST requests with custom base64-encoded payloads. Attackers can write JSP webshells to the web root and execute them through the web server to achieve arbitrary OS command execution with web server privileges. Exploitation evidence was first observed by the Shadowserver Foundation on 2021-03-26 (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

Seeyon OA A8 has an unauthenticated arbitrary file write vulnerability in the /seeyon/htmlofficeservlet endpoint. Attackers can send specially crafted POST requests with custom base64-encoded payloads to write arbitrary files, including JSP webshells, to the web application root. This enables remote code execution with web server privileges.

MitigationApply vendor patch immediately; if unavailable, restrict network access to the vulnerable endpoint or disable the servlet, and hunt for existing webshells/compromise indicators.

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: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 Seeyon OA A8 installation
    Check for Seeyon OA installation directories (commonly under C:\Seeyon or /opt/seeyon on Linux), or look for running java processes with 'seeyon' or 'A8' in the command line
    Affected if Seeyon OA A8 software is installed on the system
  2. Verify vulnerable endpoint is accessible
    Send a GET request to http(s)://<target>/seeyon/htmlofficeservlet and check for any response (a 200, 404, or error response indicates the endpoint exists)
    Affected if The /seeyon/htmlofficeservlet endpoint responds to requests (is exposed and accessible)
  3. Inspect web root for suspicious JSP files
    Search the web application root directory (typically in the 'webapps' or 'ROOT' folder under the Seeyon installation) for newly created or unrecognized .jsp files, especially with names like shell.jsp, cmd.jsp, or random alphanumeric filenames
    Affected if Unknown or suspicious JSP files exist in the web application directory that were not placed there by administrators
  4. Check for webshell patterns in uploaded files
    Search JSP files under the web root for common webshell patterns such as 'Runtime.getRuntime()', 'ProcessBuilder', 'ProcessImpl', or base64 decode functions used for command execution
    Affected if JSP files contain code that executes system commands or shell operations
  5. Review web server access logs for exploit attempts
    Examine HTTP access logs for POST requests to /seeyon/htmlofficeservlet containing base64-encoded data or unusual request patterns
    Affected if Logs show POST requests to the vulnerable endpoint with custom payloads

A system is affected if it runs Seeyon OA A8 with the /seeyon/htmlofficeservlet endpoint exposed and accessible, or if webshell files are present in the web application 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch immediately; if unavailable, restrict network access to the vulnerable endpoint or disable the servlet, and hunt for existing webshells/compromise indicators.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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