Skip to main content
Mallory
HighVulnerability

CVE-2013-7149: SQL Injection in Revive Adserver axmlrpc.php

Published Dec 28, 2013 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS2.0%81st percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
Vendors
OpenxRevive-Adserver
IdentifiersCVE-2013-7149CWE-89 · Improper Neutralization of Special…

A SQL injection vulnerability exists in the www/delivery/axmlrpc.php script (the XML-RPC delivery invocation script) in Revive Adserver versions prior to 3.0.2 and OpenX Source 2.8.11 and earlier. The vulnerability is due to improper sanitization of the 'what' parameter in XML-RPC method calls, allowing remote attackers to inject and execute arbitrary SQL commands.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary SQL commands on the backend database, potentially leading to data exfiltration, modification, or deletion, as well as possible compromise of the application and underlying server.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict access to the axmlrpc.php script via network controls or web server configuration, and implement input validation and sanitization for the 'what' parameter to prevent SQL injection.

Remediation

Patch, then assume compromise.

Upgrade Revive Adserver to version 3.0.2 or later, or OpenX Source to a version beyond 2.8.11, where the input validation and sanitization for the 'what' parameter in axmlrpc.php has been properly implemented.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenxOpenxapplication
Revive-AdserverRevive Adserverapplication
FAQ

Frequently asked questions

Is CVE-2013-7149 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2013-7149?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2013-7149.
Is there a patch for CVE-2013-7149?
Upgrade Revive Adserver to version 3.0.2 or later, or OpenX Source to a version beyond 2.8.11, where the input validation and sanitization for the 'what' parameter in axmlrpc.php has been properly implemented.
What products are affected by CVE-2013-7149?
Openx and Revive-Adserver Revive Adserver.
How severe is CVE-2013-7149?
CVE-2013-7149 has a CVSS v2 score of 7.5 (High) and an EPSS score of 2.0% (81st percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.