CVE-2017-18521

HIGHNVD 8.88.8—

8.8

The democracy-poll plugin before 5.4 for WordPress has CSRF via wp-admin/options-general.php?page=democracy-poll&subpage=l10n.

CVSS v3: 8.8
EG Score: 8.8(medium)
EPSS: 28.9%
KEV: Not listed

Published

August 21, 2019

Last Modified

November 21, 2024

References (4)

cve@mitrehttps://wordpress.org/plugins/democracy-poll/#developers
cve@mitrehttps://www.pluginvulnerabilities.com/2017/02/22/cross-site-request-forgery-csrfcross-site-scripting-xss-vulnerability-in-democracy-poll/
af854a3a-2127-422b-91ae-364da2661108https://wordpress.org/plugins/democracy-poll/#developers
af854a3a-2127-422b-91ae-364da2661108https://www.pluginvulnerabilities.com/2017/02/22/cross-site-request-forgery-csrfcross-site-scripting-xss-vulnerability-in-democracy-poll/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-352Cross-Site Request Forgery (CSRF)

Data Freshness Timeline

(refreshed 9× in last 7d / 19× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:49 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 22:28 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:41 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-28 13:42 UTCepss_batch
2026-05-27 15:30 UTCEG score recompute
2026-05-27 15:30 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2017-18521?

CVE-2017-18521 is a high vulnerability published on August 21, 2019. The democracy-poll plugin before 5.4 for WordPress has CSRF via wp-admin/options-general.php?page=democracy-poll&subpage=l10n.

When was CVE-2017-18521 disclosed?

CVE-2017-18521 was first published in the National Vulnerability Database on August 21, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2017-18521 actively exploited?

CVE-2017-18521 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2017-18521?

CVE-2017-18521 has a CVSS v3 base score of 8.8 (NVD).

How do I remediate CVE-2017-18521?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-18521, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-18521

Explore →

Is Your Infrastructure Affected by CVE-2017-18521?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2017-18521

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2017-18521?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)