How severe is GHSA-44v2-prcf-pc3m?

No CVSS score has been assigned to GHSA-44v2-prcf-pc3m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-44v2-prcf-pc3m?

GHSA-44v2-prcf-pc3m affects the following packages: joomla/database (Packagist), joomla/database (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-44v2-prcf-pc3m?

Update joomla/database to 3.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-44v2-prcf-pc3m is resolved across your whole dependency graph.

How do I detect GHSA-44v2-prcf-pc3m in my Packagist dependencies?

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

How do I mitigate GHSA-44v2-prcf-pc3m 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 GHSA-44v2-prcf-pc3m actively exploited in the wild?

No public exploit code has been indexed for GHSA-44v2-prcf-pc3m 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 GHSA-44v2-prcf-pc3m?

GHSA-44v2-prcf-pc3m has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th 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 GHSA-44v2-prcf-pc3m?

GHSA-44v2-prcf-pc3m 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 GHSA-44v2-prcf-pc3m published, and has it been updated?

GHSA-44v2-prcf-pc3m was published on April 8, 2025 and was last updated on June 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Joomla Framework Database Package Vulnerable to SQL…

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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 GHSA-44v2-prcf-pc3m.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

🐘joomla/database🐘joomla/database

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

Improper handling of identifiers lead to a SQL injection vulnerability in the quoteNameStr method of the database package. Please note: the affected method is a protected method. It has no usages in the original packages in neither the 2.x nor 3.x branch and therefore the vulnerability in question can not be exploited when using the original database class. However, classes extending the affected class might be affected, if the vulnerable method is used.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`joomla/database`	≥ 3.0.0&&< 3.4.0	3.4.0`composer require joomla/database:^3.4.0`
🐘Packagist	`joomla/database`	≥ 1.0.0&&< 2.2.0	2.2.0`composer require joomla/database:^2.2.0`

Affected Products

1 product · 2 configurations

Application

joomla\!joomla

≥ 3.0.0 && < 3.4.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for joomla/database, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update joomla/database to 3.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-44v2-prcf-pc3m 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

Improper handling of identifiers lead to a SQL injection vulnerability in the quoteNameStr method of the database package. Please note: the affected method is a protected method. It has no usages in the original packages in neither the 2.x nor 3.x branch and therefore the vulnerability in question can not be exploited when using the original database class. However, classes extending the affected class might be affected, if the vulnerable method is used.

O3 Security · Impact-Aware SCA

Is GHSA-44v2-prcf-pc3m in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Joomla Framework Database Package Vulnerable to SQL InjectionGHSA-44v2-prcf-pc3m