Skip to main content
Menu
CVEs

CVE

FIT2CLOUD MeterSphere remote code execution via unauthenticated plugin endpoints

Affects MeterSphere 1.13.0 to before 1.14.7 and 1.15.0 to before 1.16.4, where /plugin/** endpoints allow anonymous access. Fixed in 1.14.7 and 1.16.4.

CVE-2022-51027Published Updated Summary written by a model

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.14.7, 1.16.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 1.14.7, 1.16.4.

Summary

MeterSphere versions 1.13.0 before 1.14.7 and 1.15.0 before 1.16.4 contain a pre-authentication code injection vulnerability due to the /plugin/** endpoints being exposed with anonymous access. Attackers can upload a malicious jar via POST /plugin/add and invoke it through POST /plugin/customMethod using the 'entry' and 'request' parameters, which are passed to Class.forName and method invocation for remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-14.

Who should check

Teams running the MeterSphere test platform, including self-hosted instances exposed to a network, on affected builds.

“MeterSphere is susceptible to remote code execution.”

github.com

cve.now Index

45Pcve.now Index 45 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 50 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 1.14.7, 1.16.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2022-51027 (MeterSphere < 1.14.7 / 1.16.4 Pre-Auth RCE via /plugin/customMethod), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2022-51027 (entry last updated 2026-11-18):
Affected:
- FIT2CLOUD MeterSphere: from 1.13.0, fixed in 1.14.7; from 1.15.0, fixed in 1.16.4
Fixed versions: 1.14.7, 1.16.4.
Conditions (all must be true for the bug to be hit):
- The /plugin/** endpoints are reachable with anonymous access in affected builds. (source: https://github.com/metersphere/metersphere/commit/07155cf833)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2022-51027 is not listed as of cve.now's last read.
This KEV status is for CVE-2022-51027 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/metersphere/metersphere/commit/07155cf833
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/metersphere/metersphere-plugin-rce.yaml
- https://www.vulncheck.com/advisories/metersphere-1.13.0-1.16.3-pre-auth-rce-via-plugin-custommethod
- https://www.vulncheck.com/advisories/metersphere-1.14.7-1.16.4-pre-auth-rce-via-plugin-custommethod
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2022-51027
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2022-51027"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  4. Record last updated

Affected versions

  • FIT2CLOUD MeterSphere

    From 1.13.0 · fixed in 1.14.7; From 1.15.0 · fixed in 1.16.4

Evidence 7

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2022-51027

Is CVE-2022-51027 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The /plugin/** endpoints in affected MeterSphere builds can be reached without logging in, and the advisory says this leads to remote code execution on the MeterSphere server.Source: github.com, github.com

Which versions are affected by CVE-2022-51027?

MeterSphere: from 1.13.0 before 1.14.7; from 1.15.0 before 1.16.4.Source: cve.now feed data

Am I affected, and how do I check?

Affected builds are 1.13.0 up to 1.14.7 and 1.15.0 up to 1.16.4. The exposure comes from the /plugin/** endpoints being set to anonymous access, so check the installed version number against these ranges.Source: github.com, github.com

How do I fix CVE-2022-51027?

Upgrade to MeterSphere 1.14.7 or 1.16.4, depending on which release line is in use.Source: github.com, github.com

More CVEs