How severe is CVE-2013-4662?

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

Which packages are affected by CVE-2013-4662?

CVE-2013-4662 affects the following packages: civicrm/civicrm-core (Packagist), civicrm/civicrm-core (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2013-4662?

Update civicrm/civicrm-core to 4.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4662 is resolved across your whole dependency graph.

How do I detect CVE-2013-4662 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for civicrm/civicrm-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2013-4662?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-4662 can be triaged on real exposure rather than presence alone.

Is CVE-2013-4662 actively exploited in the wild?

No public exploit code has been indexed for CVE-2013-4662 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2013-4662?

CVE-2013-4662 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 62th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2013-4662?

CVE-2013-4662 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.

When was CVE-2013-4662 published, and has it been updated?

CVE-2013-4662 was published on May 17, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2013-4662 — civicrm/civicrm-core

CVE-2013-4662 is a SQL Injection vulnerability in civicrm/civicrm-core. A fix is available for civicrm/civicrm-core — see the affected versions and patch details below.

CiviCRM SQL injection vulnerability via Quick Search API

Published

May 17, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

2 pkgs affected

🐘civicrm/civicrm-core🐘civicrm/civicrm-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

The Quick Search API in CiviCRM 4.2.0 through 4.2.9 and 4.3.0 through 4.3.3 allows remote authenticated users to bypass the validation layer and conduct SQL injection attacks via a direct request to the "second layer" of the API, related to contact.getquick.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`civicrm/civicrm-core`	≥ 4.2.0&&< 4.2.9	4.2.9`composer require civicrm/civicrm-core:^4.2.9`
🐘Packagist	`civicrm/civicrm-core`	≥ 4.3.0&&< 4.3.3	4.3.3`composer require civicrm/civicrm-core:^4.3.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for civicrm/civicrm-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update civicrm/civicrm-core to 4.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2013-4662 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2013-4662 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2013-4662. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2013-4662 in your dependencies?

O3 Security finds CVE-2013-4662 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works