Revive Adserver before 3.2.2 does not restrict access to run-mpe.php, which allows remote attackers to run the Maintenance Priority Engine…

published 2015-10-14 11y ago modified 2026-06-17 4mo ago also EUVD-2015-7295

cvss: 5.0; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 2.6%; EPSS 2.6% chance of exploitation in 30 days, percentile 85%
public exploits: 0; none known

Revive Adserver before 3.2.2 does not restrict access to run-mpe.php, which allows remote attackers to run the Maintenance Priority Engine and possibly cause a denial of service (resource consumption) via a direct request.

Is CVE-2015-7371 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

2.59% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness

CWE-264 Permissions, Privileges, and Access Controls
CWE-399 Resource Management Errors

References

revive-adserver.com /security/revive-sa-2015-001
vendor-advisory
securityfocus.com /archive/1/536633/100/0/threaded
mailing-list
seclists.org /fulldisclosure/2015/Oct/32
mailing-list
packetstormsecurity.com /files/133893/Revive-Adserver-3.2.1-CSRF-XSS-Local-File-Inclusion.html

Sources

CVE List CVE-2015-7371
NVD CVE-2015-7371

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.