CVE-2017-5611 [Critical] | SQL Injection in Wordpress

CVE-2017-5611 is rated High Risk (70/100): CVSS Critical severity, with high exploitation likelihood (EPSS 9.93%, 95th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	12.38%	9.93%	-2.44%
2	2026-03-04	10.03%	12.38%	+2.35%
3	2026-03-01	—	10.03%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

12.38%

9.93%

-2.44%

2026-03-04

10.03%

12.38%

+2.35%

2026-03-01

—

10.03%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	[email protected]
7.5	2.0	HIGH	`AV:N/AC:L/Au:N/C:P/I:P/A:P` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:P) Partial availability impact.	10.0	6.4	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

[email protected]

7.5

2.0

HIGH

AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:P): Partial availability impact.

10.0

6.4

[email protected]

OS Trackers for CVE-2017-5611

vendor	priority	summary	link
`debian`	not yet assigned	CVE-2017-5611 not yet assigned priority: Debian including 1 source packages (wordpress), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2017-5611
`ubuntu`	medium	CVE-2017-5611 medium priority: Ubuntu including 1 source packages (wordpress), 23 status rows across 23 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, precise, questing, trusty, upstream, xenial, yakkety, zesty): not-affected 18, ignored 2, DNE 1, needed 1, released 1.	https://ubuntu.com/security/CVE-2017-5611

Affected software / configurations for CVE-2017-5611

Vendor	Product	Version	Raw CPE
wordpress	wordpress	<= 4.7.1	cpe:2.3:a:wordpress:wordpress::::::::
debian	debian_linux	8.0	cpe:2.3:o:debian:debian_linux:8.0:::::::*
debian	debian_linux	9.0	cpe:2.3:o:debian:debian_linux:9.0:::::::*
oracle	data_integrator	11.1.1.9.0	cpe:2.3:a:oracle:data_integrator:11.1.1.9.0:::::::*
oracle	data_integrator	12.2.1.3.0	cpe:2.3:a:oracle:data_integrator:12.2.1.3.0:::::::*
oracle	data_integrator	12.2.1.4.0	cpe:2.3:a:oracle:data_integrator:12.2.1.4.0:::::::*

References for CVE-2017-5611

URL	Tags
http://www.debian.org/security/2017/dsa-3779	Third Party Advisory
http://www.openwall.com/lists/oss-security/2017/01/28/5	Mailing List Patch Third Party Advisory
http://www.securityfocus.com/bid/95816	Third Party Advisory VDB Entry
http://www.securitytracker.com/id/1037731	Third Party Advisory VDB Entry
https://codex.wordpress.org/Version_4.7.2	Release Notes Vendor Advisory
https://github.com/WordPress/WordPress/commit/85384297a60900004e27e417eac56d24267054cb	Patch Third Party Advisory
https://wordpress.org/news/2017/01/wordpress-4-7-2-security-release/	Patch Vendor Advisory
https://wpvulndb.com/vulnerabilities/8730	Patch Third Party Advisory
https://www.oracle.com/security-alerts/cpujan2021.html	Third Party Advisory

URL

CVE-2017-5611

Exploit prediction scoring system (EPSS) score for CVE-2017-5611

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5611

Weakness enumeration for CVE-2017-5611

OS Trackers for CVE-2017-5611

Affected software / configurations for CVE-2017-5611

References for CVE-2017-5611