On this page (7 sections)

CVE-2021-48023 is an unrestricted file upload vulnerability in Weaver E-cology 9.0, an enterprise office automation platform. According to the NVD record, an unauthenticated attacker can upload arbitrary JSP files through a single endpoint and reach remote code execution on the server.

If you run E-cology 9.0, host it for a client, or operate a network where it is reachable from the internet, treat this as urgent. The record also notes exploitation evidence, which makes checking for existing compromise as important as closing the hole.

What happened

The NVD entry, published 2026-11-18, describes a flaw in the file upload handler at /page/exportImport/uploadOperation.jsp. The endpoint accepts uploads from unauthenticated users and does not restrict the file type, so a JSP file can be stored on the server. The description says uploaded files land in /page/exportImport/fileTransfer/, from where they can be requested and executed by the Java application server.

The description also states that the Shadowserver Foundation first observed exploitation evidence on 2023-10-20. That is the only exploitation detail in the sources. We have no information on the scale of attacks, who carried them out, or which victims were affected, so none of that is claimed here.

Only one independent publisher covers this story so far, and the NVD record is the main primary source. The references listed there include a VulnCheck advisory and a Nuclei template. We have not been able to confirm vendor guidance or a patched version.

How the weakness works

CWE-434 describes applications that let users upload files without properly checking what they are. On a Java platform the risk is especially high: if an uploaded .jsp file is saved inside a directory the application server serves, the server will compile and run it as code the next time someone requests that URL. The uploaded file is effectively a webshell, giving the attacker the same privileges as the application server process.

Two things make this case severe. First, no login is required, so anyone who can reach the endpoint can attempt it. Second, the code runs on the server itself, which can expose internal documents, credentials stored in configuration files and the internal network the server can reach.

Who is affected

  • Organizations running Weaver E-cology 9.0, including agencies and hosting providers who manage it for others.
  • Servers where the E-cology web interface is reachable from the internet or from a large internal network.
  • Environments where the application server runs with broad file system or network privileges, which increases the damage after a successful upload.

The sources do not list exact build numbers inside the 9.0 line, so assume any E-cology 9.0 installation is in scope until the vendor or your integrator confirms otherwise.

How to check your exposure

Start by finding out whether the endpoint answers from outside your network, and then look for files that should not be there.

  1. Inventory every E-cology instance you run or host, and note the version shown in the admin interface or documented by your integrator.
  2. From a machine outside your network, check whether the web interface is reachable at all. If it does not need to be public, that is the first thing to change.
  3. Search your web server and application server access logs for requests to /page/exportImport/uploadOperation.jsp, particularly POST requests from unfamiliar addresses.
  4. Inspect the /page/exportImport/fileTransfer/ directory for JSP files you did not create.

This read-only command lists JSP files in the upload directory on a Linux server. Replace the placeholder with your actual web root, and look for any result you cannot explain:

List JSP files in the upload directory (Linux, read-only)Shell
find /path/to/ecology/page/exportImport/fileTransfer/ -type f -name '*.jsp' -ls

This command searches an access log for requests to the vulnerable endpoint. Adjust the log path to your server. Any hit from an address you do not recognize deserves investigation:

Search an access log for the vulnerable endpoint (Linux, read-only)Shell
grep 'uploadOperation.jsp' /path/to/access.log
Caution. A missing file does not prove you were not compromised. An attacker may have deleted their upload after use or moved to other persistence. Treat any suspicious request in the logs as a possible incident.

What to do now

No fixed version is named in the available sources, so the steps below focus on contacting the vendor, reducing exposure and checking for compromise.

  1. Contact Weaver or your E-cology integrator and ask for the official fix or mitigation for CVE-2021-48023, and confirm which builds are covered.
  2. Remove E-cology from direct internet exposure. Place it behind a VPN or an IP allowlist until a fix is confirmed.
  3. Block or restrict requests to /page/exportImport/uploadOperation.jsp at your reverse proxy or firewall if the feature is not needed.
  4. Prevent the application server from executing files in /page/exportImport/fileTransfer/ where your configuration allows it.
  5. Review the upload directory and logs as described above, and preserve copies before deleting anything.
  6. If you find unknown JSP files or suspicious requests, isolate the server, rotate credentials and secrets stored on it, and follow an incident response process.
  7. Run the application server under a least-privilege account so a webshell has limited reach.
Tip. Preserve evidence first. Copy suspicious files and logs to a separate location before cleaning up, so you can work out what was accessed. Our guide on what to do when a website is hacked walks through the process.

Detection and monitoring afterwards

File upload flaws often leave quiet traces, so keep watching after you apply mitigations.

  • Alert on new or modified .jsp files under the E-cology web root, especially in upload directories.
  • Watch access logs for POST requests to upload endpoints followed shortly by GET requests to newly created files.
  • Monitor outbound connections from the application server for destinations it does not normally contact.
  • Review unexpected child processes launched by the Java application server.

A web application firewall can add a layer by filtering requests to known risky paths, as explained in what a WAF is, but it is not a substitute for a vendor fix. For outside-in checks, Webforta Scan can run read-only scans of sites you verify, and the malware detection overview explains what an external view can and cannot see on a compromised server.

Timeline

Dates stated in the research
DateEvent
2023-10-20Shadowserver Foundation first observes exploitation evidence (per the NVD description)
2026-11-18CVE-2021-48023 published in NVD with CVSS 9.3

The sources do not say when the vendor was notified or whether a patch exists, so those points are left open.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2021-48023: Weaver E-cology 9.0 contains an unrestricted file upload vulnerability in /page/exportImport/uploadOperation.jsp that allows unauthenticated attackers to…nvd.nist.gov ·
  • CVE-2021-48023
  • Weaver E-cology
  • file upload
  • webshell
  • RCE