CVE-2018-16552: MicroPyramid Django-CRM 0.2 allows CSRF for /users/create/, /users/##/edit/, and /accounts/##/delete/ URIs.

This month

HIGH 8.8DOWNGRADE

CVE-2018-16552 is a high-severity flaw (CVSS 8.8) affecting django crm. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

MicroPyramid Django-CRM 0.2 allows CSRF for /users/create/, /users/##/edit/, and /accounts/##/delete/ URIs.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.6% (top 49%)
CISA exploited list	No
Weakness	CWE-352
Published	2018-09-05
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: micropyramid

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

Am I affected?

Timeline

2018-09-05 22:29 UTCPublished CVE record published
2026-06-17 01:44 UTCUpdated Record last modified

micropyramid django crm DOWNGRADE

Affected: 0.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.2

1. Check installed version

apt-cache policy django-crm || rpm -q django-crm || django-crm --version

2. No fixed release: DOWNGRADE to a release before 0.2 (Debian / Ubuntu)

apt-cache madison django-crm sudo apt install django-crm=<VERSION_BEFORE_0.2> sudo apt-mark hold django-crm

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list django-crm sudo dnf downgrade django-crm-<VERSION_BEFORE_0.2> sudo dnf versionlock add django-crm

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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-2018-16552?

django crm: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-16552 being exploited?

CVE-2018-16552 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-2018-16552 affect?

CVE-2018-16552 affects django crm. Severity is high (CVSS 8.8). MicroPyramid Django-CRM 0.2 allows CSRF for /users/create/, /users/##/edit/, and /accounts/##/delete/ URIs.

How urgent is CVE-2018-16552?

Priority 48/100. High severity; Public exploit reference

Software pages

Django vulnerabilities

Related CVEs

CVE-2019-11457 HIGH 8.8 DOWNGRADE Multiple CSRF issues exist in MicroPyramid Django CRM 0.2.1 via /change-password-by-admin/, /api/settings/add/

References

← Back to latest CVEs