CVE-2014-2550: Cross-site request forgery (CSRF) vulnerability in the Disable Comments plugin before 1.0.4 for WordPress allo

Q: How do I fix CVE-2014-2550?

disable comments project: upgrade to 1.0.4. Exact commands for each OS are on this page.

Q: Is CVE-2014-2550 being exploited?

CVE-2014-2550 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-2014-2550 affect?

CVE-2014-2550 affects disable comments project. Severity is high (CVSS 8.8). Cross-site request forgery (CSRF) vulnerability in the Disable Comments plugin before 1.0.4 for WordPress allows remote attackers to hijack the authentication of administrators for requests that enable comments via a request to the disable_

Q: How urgent is CVE-2014-2550?

Priority 55/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2014-2550 is a high-severity flaw (CVSS 8.8) affecting disable comments project. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Cross-site request forgery (CSRF) vulnerability in the Disable Comments plugin before 1.0.4 for WordPress allows remote attackers to hijack the authentication of administrators for requests that enable comments via a request to the disable_comments_settings page to wp-admin/options-general.php.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): MITRE · Vendor: disable comments

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

Am I affected?

Timeline

2018-03-19 21:29 UTCPublished CVE record published
2026-06-17 00:06 UTCUpdated Record last modified

disable comments disable comments project UPGRADE

Affected: < 1.0.4

Fixed in: 1.0.4

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy disable-comments-project || rpm -q disable-comments-project || disable-comments-project --version

2. UPGRADE to 1.0.4 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade disable-comments-project

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade disable-comments-project

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-2014-2550?

disable comments project: upgrade to 1.0.4. Exact commands for each OS are on this page.

Is CVE-2014-2550 being exploited?

CVE-2014-2550 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-2014-2550 affect?

CVE-2014-2550 affects disable comments project. Severity is high (CVSS 8.8). Cross-site request forgery (CSRF) vulnerability in the Disable Comments plugin before 1.0.4 for WordPress allows remote attackers to hijack the authentication of administrators for requests that enable comments via a request to the disable_

How urgent is CVE-2014-2550?

Priority 55/100. High severity; Public exploit reference

Software pages

WordPress vulnerabilities · PHP vulnerabilities

References

← Back to latest CVEs