How severe is CVE-2014-3704?

No CVSS score has been assigned to CVE-2014-3704 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2014-3704?

CVE-2014-3704 affects the following products: debian debian linux, drupal drupal.

How do I patch CVE-2014-3704?

Apply the debian debian linux security patch or hotfix for CVE-2014-3704 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2014-3704 across my infrastructure?

Inventory every debian debian linux deployment and check each version against the affected-products list above.

How do I mitigate CVE-2014-3704 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2014-3704 actively exploited in the wild?

Yes. There are 18 known exploit references for CVE-2014-3704, including 5 documented proof-of-concept exploits on Exploit-DB and 12 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-3704?

CVE-2014-3704 has an EPSS (Exploit Prediction Scoring System) score of 100.0%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2014-3704?

CVE-2014-3704 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2014-3704?

CVE-2014-3704 affects debian debian linux (1 version, e.g. 7.0); drupal drupal. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2014-3704?

A Nuclei detection template exists for CVE-2014-3704, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2014-3704 published, and has it been updated?

CVE-2014-3704 was published on October 16, 2014 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2014-3704 — Debian Linux

CVE-2014-3704 is a SQL Injection vulnerability in debian debian linux. 18 public exploit references exist, so weaponization risk is real. A fix is available — see the affected versions and patch details below.

The expandArguments function in the database abstraction API in Drupal core 7.x before 7.32 does not properly construct prepared statements, which allows remote attackers to conduct…

Published

Oct 16, 2014

Updated

Jun 17, 2026

Affected

2 products

Patched

See advisory

Exploits

18 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

100.0%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The expandArguments function in the database abstraction API in Drupal core 7.x before 7.32 does not properly construct prepared statements, which allows remote attackers to conduct SQL injection attacks via an array containing crafted keys.

Affected Products

2 products · 2 configurations

debian linuxdebian

1 version

7.0

Application

drupaldrupal

≥ 7.0 && < 7.32

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-34984webappsphp✓ Verified

Drupal 7.0 < 7.31 - 'Drupalgeddon' SQL Injection (PoC) (Reset Password) (1)

by stopstene · Oct 16, 2014

Exploit-DB Source

EDB-44355webappsphp

Drupal 7.0 < 7.31 - 'Drupalgeddon' SQL Injection (Admin Session)

by Stefan Horst · Nov 3, 2014

Exploit-DB Source

EDB-34993webappsphp✓ Verified

Drupal 7.0 < 7.31 - 'Drupalgeddon' SQL Injection (PoC) (Reset Password) (2)

by Dustin Dörr · Oct 17, 2014

Exploit-DB Source

EDB-34992webappsphp✓ Verified

Drupal 7.0 < 7.31 - 'Drupalgeddon' SQL Injection (Add Admin User)

by Claudio Viviani · Oct 17, 2014

Exploit-DB Source

EDB-35150webappsphp✓ Verified

Drupal 7.0 < 7.31 - 'Drupalgeddon' SQL Injection (Remote Code Execution)

by Stefan Horst · Nov 3, 2014

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every debian debian linux deployment and check each version against the affected-products list above.
Fix
Apply the debian debian linux security patch or hotfix for CVE-2014-3704 on the affected version, following the vendor advisory for your exact build.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

How to detect CVE-2014-3704

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2014-3704 -u https://target

Template: Drupal SQL Injection
Severity: high
Impact: Successful exploitation of this vulnerability can lead to unauthorized access, data leakage, and potential compromise of the Drupal application and its underlying database.
Remediation: Upgrade to Drupal core 7.32 or later.

Template by ProjectDiscovery nuclei-templates (princechaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2014-3704 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVE-2014-3704 — Debian Linux

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2014-3704

Frequently Asked Questions

Is CVE-2014-3704 being exploited in your environment?