How severe is CVE-2022-36553?

No CVSS score has been assigned to CVE-2022-36553 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-36553?

Affected package information for CVE-2022-36553 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-36553?

No fixed release is recorded for CVE-2022-36553 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2022-36553 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2022-36553 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2022-36553 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2022-36553, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-36553?

CVE-2022-36553 has an EPSS (Exploit Prediction Scoring System) score of 90.9%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2022-36553?

CVE-2022-36553 is classified as CWE-77 (CWE-77). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2022-36553?

A Nuclei detection template exists for CVE-2022-36553, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-36553 published, and has it been updated?

CVE-2022-36553 was published on August 29, 2022 and was last updated on August 3, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2022-36553 — Nwqda

CVE-2022-36553 is a CWE-77 vulnerability. 2 public exploit references exist, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Hytec Inter HWL-2511-SS v1.05 and below was discovered to contain a command injection vulnerability via the component /www/cgi-bin/popen.cgi.

Published

Aug 29, 2022

Updated

Aug 3, 2024

Affected

1 product

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.9%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

Hytec Inter HWL-2511-SS v1.05 and below was discovered to contain a command injection vulnerability via the component /www/cgi-bin/popen.cgi.

Affected Products

1 product · 1 configurations

hwl-2511-ss firmwarehytec

≤ 1.05

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Hytec Inter HWL-2511-SS v1.05 and below was discovered to contain a comm…

github.comGithubJan 2024

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2022-36553 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

How to detect CVE-2022-36553

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2022-36553 -u https://target

Template: Hytec Inter HWL-2511-SS - Remote Command Execution
Severity: critical
Impact: Unauthenticated attackers can execute arbitrary commands on the Hytec Inter HWL-2511-SS cellular router through command injection in the popen.cgi endpoint, potentially gaining complete control over the device and connected network infrastructure.
Remediation: Update Hytec Inter HWL-2511-SS firmware to a version later than 1.05 that properly sanitizes command parameters in popen.cgi.

Template by ProjectDiscovery nuclei-templates (HuTa0), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Hytec Inter HWL-2511-SS v1.05 and below was discovered to contain a command injection vulnerability via the component /www/cgi-bin/popen.cgi.

O3 Security · Impact-Aware SCA

Is CVE-2022-36553 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2022-36553 — Nwqda

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2022-36553

Frequently Asked Questions

Is CVE-2022-36553 in your dependencies?