CVE-2017-20173: A vulnerability was found in AlexRed contentmap

Q: How do I fix CVE-2017-20173?

contentmap: upgrade to 2017-03-08. Exact commands for each OS are on this page.

Q: Is CVE-2017-20173 being exploited?

CVE-2017-20173 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-2017-20173 affect?

CVE-2017-20173 affects contentmap. Severity is medium (CVSS 5.5). A vulnerability was found in AlexRed contentmap. It has been rated as critical. Affected by this issue is the function Load of the file contentmap.php. The manipulation of the argument contentid leads to sql injection. The name of the patch

Q: How urgent is CVE-2017-20173?

Priority 32/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

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

A vulnerability was found in AlexRed contentmap. It has been rated as critical. Affected by this issue is the function Load of the file contentmap.php. The manipulation of the argument contentid leads to sql injection. The name of the patch is dd265d23ff4abac97422835002c6a47f45ae2a66. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-218492.

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.6% (top 49%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-01-18
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: contentmap project

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

Am I affected?

Timeline

2023-01-18 16:15 UTCPublished CVE record published
2026-06-17 01:15 UTCUpdated Record last modified

contentmap project contentmap UPGRADE

Affected: < 2017-03-08

Fixed in: 2017-03-08

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy contentmap || rpm -q contentmap || contentmap --version

2. UPGRADE to 2017-03-08 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade contentmap

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade contentmap

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-2017-20173?

contentmap: upgrade to 2017-03-08. Exact commands for each OS are on this page.

Is CVE-2017-20173 being exploited?

CVE-2017-20173 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-2017-20173 affect?

CVE-2017-20173 affects contentmap. Severity is medium (CVSS 5.5). A vulnerability was found in AlexRed contentmap. It has been rated as critical. Affected by this issue is the function Load of the file contentmap.php. The manipulation of the argument contentid leads to sql injection. The name of the patch

How urgent is CVE-2017-20173?

Priority 32/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

References

← Back to latest CVEs