How severe is CVE-2016-9124?

CVE-2016-9124 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2016-9124 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-9124?

CVE-2016-9124 affects Revive-adserver Revive Adserver. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2016-9124?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2016-9124 published?

CVE-2016-9124 was published on 2017-03-28 and last updated on 2026-06-17.

CVE-2016-9124

CVE-2016-9124 is a critical-severity vulnerability in Revive-adserver Revive Adserver with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-287.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 5.0
EPSS exploit prediction: 2% (81st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-287
Affected product: Revive-adserver Revive Adserver
Published: 2017-03-28
Last modified: 2026-06-17

Description

Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts. The login page of Revive Adserver is vulnerable to password-guessing attacks. An account lockdown feature was considered, but rejected to avoid introducing service disruptions to regular users during such attacks. A random delay has instead been introduced as a countermeasure in case of password failures, along with a system to discourage parallel brute forcing. These systems will effectively allow the valid users to log in to the adserver, even while an attack is in progress.

Frequently asked questions

What is CVE-2016-9124?: Revive Adserver before 3.2.3 suffers from Improper Restriction of Excessive Authentication Attempts. The login page of Revive Adserver is vulnerable to password-guessing attacks. An account lockdown feature was considered, but rejected to avoid introducing service disruptions to regular users during such attacks. A random delay has instead been introduced as a countermeasure in case of password failures, along with a system to discourage parallel brute forcing. These systems will effectively allow the valid users to log in to the adserver, even while an attack is in progress.
How severe is CVE-2016-9124?: CVE-2016-9124 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-9124 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (81st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-9124?: CVE-2016-9124 affects Revive-adserver Revive Adserver. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-9124?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2016-9124 published?: CVE-2016-9124 was published on 2017-03-28 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:revive-adserver:revive_adserver:*:*:*:*:*:*:*:*

More vulnerabilities in Revive-adserver Revive Adserver

CVE-2016-9125 — Critical (CVSS 9.8): Revive Adserver before 3.2.3 suffers from session fixation, by allowing arbitrary session identifiers to be forced and,…
CVE-2017-5830 — Critical (CVSS 9.8): Revive Adserver before 4.0.1 allows remote attackers to execute arbitrary code via serialized data in the cookies…
CVE-2016-9470 — Critical (CVSS 9.0): Revive Adserver before 3.2.5 and 4.0.0 suffers from Reflected File Download. `www/delivery/asyncspc.php` was vulnerable…
CVE-2026-50741 — High (CVSS 8.8): Bypass to the fix for CVE-2026-34916. Variants of such vectors have been also reported by phucrio and offsetmd. The fix…
CVE-2025-48986 — High (CVSS 8.8): Authorization bypass in Revive Adserver 5.5.2 and 6.0.1 and earlier versions causes an logged in attacker to change…
CVE-2025-52664 — High (CVSS 8.8): SQL injection in Revive Adserver 6.0.0 causes potential disruption or information access when specifically crafted…

All CVEs affecting Revive-adserver Revive Adserver →

Other CWE-287 (Improper Authentication) vulnerabilities

CVE-2026-20317 — Critical (CVSS 10.0): As part of Cisco's ongoing commitment to proactive security and product quality, the Cisco Secure Workload engineering…
CVE-2026-19977 — Critical (CVSS 10.0): A vulnerability was detected in EFM ipTIME A3004T 14.19.0. The affected element is the function…
CVE-2026-59500 — Critical (CVSS 10.0): CWE-287: Improper Authentication
CVE-2024-27253 — Critical (CVSS 10.0): IBM DOORS Next 7.0.3 through 7.0.3 Interim Fix 018 could allow an authenticated user to bypass security logic to…
CVE-2026-56162 — Critical (CVSS 10.0): Improper authentication in Azure SQL Database allows an unauthorized attacker to elevate privileges over a network.
CVE-2026-62825 — Critical (CVSS 10.0): Improper authentication in Azure Key Vault allows an unauthorized attacker to elevate privileges over a network.

Browse all CWE-287 (Improper Authentication) vulnerabilities →