# CVE-2021-47747: meterN 1.2.3 Authenticated Remote Code Execution via Admin Scripts

> Authenticated attackers can execute arbitrary system commands with administrative privileges via vulnerable admin scripts in meterN.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Dec 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-6596-h2j7-v8m3

## What is CVE-2021-47747?

CVE-2021-47747 is a high-severity command injection vulnerability in meterN, published on 31 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

meterN 1.2.3 contains an authenticated remote code execution vulnerability in admin_meter2.php and admin_indicator2.php scripts. Attackers can exploit the 'COMMANDx' and 'LIVECOMMANDx' POST parameters to execute arbitrary system commands with administrative privileges.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2021-47747?


## How do I fix CVE-2021-47747?

No fix has been published for CVE-2021-47747 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-47747 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47747 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-47747 and fix it if it is affected.

What it is: CVE-2021-47747 is a high-severity command injection vulnerability in meterN, published on 31 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-47747 exists.

Affected product: meterN. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-47747/ (Markdown: https://insights.sbomify.com/CVE-2021-47747/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-47747
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-47747
- OSV: https://osv.dev/vulnerability/CVE-2021-47747

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-47747/
Summaries are generated and may contain mistakes; the official description above is the record.