Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2013-4599: The Misery module 6.x-2.x before 6.x-2.5 and 7.x-2.x before 7.x-2.2 for Drupal, when the "delay misery" config

33
Routine
MEDIUM 4.3DOWNGRADE

CVE-2013-4599 is a medium-severity flaw (CVSS 4.3) affecting misery. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The Misery module 6.x-2.x before 6.x-2.5 and 7.x-2.x before 7.x-2.2 for Drupal, when the "delay misery" configuration is set to a high value, allows remote attackers to cause a denial of service (process consumption) via multiple requests.

Why this priority

  • No elevated risk signals yet

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

Risk facts

CVSS score4.3 (Medium)
EPSS exploit chance1.3% (top 29%)
CISA exploited listNo
WeaknessCWE-399
Published2014-06-09
Last modified2026-06-16
Publisher (CNA): Red Hat, Inc. · Vendor: misery project

Share: LinkedIn · X · Reddit

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

Am I affected?

Timeline

misery project misery DOWNGRADE
Affected: 6.x-2.0 · 6.x-2.1 · 6.x-2.2 · 6.x-2.3 · 6.x-2.4 · 7.x-2.0 · 7.x-2.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 6.x-2.0
1. Check installed version
apt-cache policy misery || rpm -q misery || misery --version
2. No fixed release: DOWNGRADE to a release before 6.x-2.0 (Debian / Ubuntu)
apt-cache madison misery sudo apt install misery=<VERSION_BEFORE_6.x-2.0> sudo apt-mark hold misery
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list misery sudo dnf downgrade misery-<VERSION_BEFORE_6.x-2.0> sudo dnf versionlock add misery
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-2013-4599?

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

Is CVE-2013-4599 being exploited?

CVE-2013-4599 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-2013-4599 affect?

CVE-2013-4599 affects misery. Severity is medium (CVSS 4.3). The Misery module 6.x-2.x before 6.x-2.5 and 7.x-2.x before 7.x-2.2 for Drupal, when the "delay misery" configuration is set to a high value, allows remote attackers to cause a denial of service (process consumption) via multiple requests.

How urgent is CVE-2013-4599?

Priority 33/100. No elevated risk signals yet.

Software pages

Drupal vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.