How severe is CVE-2022-24827?

CVE-2022-24827 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-24827?

CVE-2022-24827 affects the following packages: com.yahoo.elide:elide-datastore-aggregation (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-24827?

Update com.yahoo.elide:elide-datastore-aggregation to 6.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24827 is resolved across your whole dependency graph.

How do I detect CVE-2022-24827 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.yahoo.elide:elide-datastore-aggregation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24827 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.

Is CVE-2022-24827 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-24827 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-2022-24827?

CVE-2022-24827 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th 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-2022-24827?

CVE-2022-24827 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-2022-24827 published, and has it been updated?

CVE-2022-24827 was published on April 11, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2022-24827 — elide-datastore-aggregati…

HIGHFix: yahoo/elide#2581

CVE-2022-24827 is a high-severity (CVSS 8.1) SQL Injection vulnerability in com.yahoo.elide:elide-datastore-aggregation. A fix is available for com.yahoo.elide:elide-datastore-aggregation — see the affected versions and patch details below.

SQL Injection in elide-datastore-aggregation

Also known asGHSA-8xpj-9j9g-fc9r

Published

Apr 11, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-24827.

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.yahoo.elide:elide-datastore-aggregation

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

Description

Impact

When leveraging the following together:

Elide Aggregation Data Store for Analytic Queries
Parameterized Columns (A column that requires a client provided parameter)
A parameterized column of type TEXT

There is the potential for a hacker to provide a carefully crafted query that would bypass server side authorization filters through SQL injection. A recent patch to Elide 6.1.2 allowed the '-' character to be included in parameterized TEXT columns. This character can be interpreted as SQL comments ('--') and allow the attacker to remove the WHERE clause from the generated query and bypass authorization filters.

Patches

A fix is provided in Elide 6.1.4.

Workarounds

The vulnerability only exists for parameterized columns of type TEXT and only for analytic queries (CRUD is not impacted). Workarounds include leveraging a different type of parameterized column (TIME, MONEY, etc) or not leveraging parameterized columns.

For more information

If you have any questions or comments about this advisory:

Open an issue in elide
Contact us in Discord

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.yahoo.elide:elide-datastore-aggregation`	≥ 6.1.3&&< 6.1.4	6.1.4`com.yahoo.elide:elide-datastore-aggregation:6.1.4`

Affected Products

1 product · 1 configurations

Application

elideelide

1 version

6.1.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.yahoo.elide:elide-datastore-aggregation, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.yahoo.elide:elide-datastore-aggregation to 6.1.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24827 is resolved across your whole dependency graph.
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.

Frequently Asked Questions

### Impact When leveraging the following together: - Elide Aggregation Data Store for Analytic Queries - Parameterized Columns (A column that requires a client provided parameter) - A parameterized column of type TEXT There is the potential for a hacker to provide a carefully crafted query that would bypass server side authorization filters through SQL injection. A recent patch to Elide 6.1.2 allowed the '-' character to be included in parameterized TEXT columns. This character can be interpreted as SQL comments ('--') and allow the attacker to remove the WHERE clause from the generated qu