CVE-2020-36648: A vulnerability, which was classified as critical, was found in pouetnet pouet 2.0

Q: How do I fix CVE-2020-36648?

pouet2.0: upgrade to 06-22-2020. Exact commands for each OS are on this page.

Q: Is CVE-2020-36648 being exploited?

CVE-2020-36648 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-36648 affect?

CVE-2020-36648 affects pouet2.0. Severity is medium (CVSS 5.5). A vulnerability, which was classified as critical, was found in pouetnet pouet 2.0. This affects an unknown part. The manipulation of the argument howmany leads to sql injection. The identifier of the patch is 11d615931352066fb2f6dcb0742827

Q: How urgent is CVE-2020-36648?

Priority 32/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2020-36648 is a medium-severity flaw (CVSS 5.5) affecting pouet2.0. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability, which was classified as critical, was found in pouetnet pouet 2.0. This affects an unknown part. The manipulation of the argument howmany leads to sql injection. The identifier of the patch is 11d615931352066fb2f6dcb07428277c2cd99baf. It is recommended to apply a patch to fix this issue. The identifier VDB-217641 was assigned to this vulnerability.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-01-08
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: pouet

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-08 10:15 UTCPublished CVE record published
2026-06-17 03:15 UTCUpdated Record last modified

pouet pouet2.0 UPGRADE

Affected: < 06-22-2020

Fixed in: 06-22-2020

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pouet2.0 || rpm -q pouet2.0 || pouet2.0 --version

2. UPGRADE to 06-22-2020 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pouet2.0

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pouet2.0

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-36648?

pouet2.0: upgrade to 06-22-2020. Exact commands for each OS are on this page.

Is CVE-2020-36648 being exploited?

CVE-2020-36648 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-36648 affect?

CVE-2020-36648 affects pouet2.0. Severity is medium (CVSS 5.5). A vulnerability, which was classified as critical, was found in pouetnet pouet 2.0. This affects an unknown part. The manipulation of the argument howmany leads to sql injection. The identifier of the patch is 11d615931352066fb2f6dcb0742827

How urgent is CVE-2020-36648?

Priority 32/100. No elevated risk signals yet.

References

← Back to latest CVEs