How severe is GHSA-6676-cqfm-gw84?

No CVSS score has been assigned to GHSA-6676-cqfm-gw84 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6676-cqfm-gw84?

GHSA-6676-cqfm-gw84 affects the following packages: wordpress (Bitnami). Ecosystems affected: Bitnami.

How do I fix GHSA-6676-cqfm-gw84?

Update wordpress to 3.7.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6676-cqfm-gw84 is resolved across your whole dependency graph.

How do I detect GHSA-6676-cqfm-gw84 in my Bitnami dependencies?

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

How do I mitigate GHSA-6676-cqfm-gw84 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-6676-cqfm-gw84 actively exploited in the wild?

Yes. There are 20 known exploit references for GHSA-6676-cqfm-gw84, including 1 documented proof-of-concept exploit on Exploit-DB and 13 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 GHSA-6676-cqfm-gw84?

GHSA-6676-cqfm-gw84 has an EPSS (Exploit Prediction Scoring System) score of 97.8%, 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 GHSA-6676-cqfm-gw84?

GHSA-6676-cqfm-gw84 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.

Is there exploit tooling available for GHSA-6676-cqfm-gw84?

A Nuclei detection template exists for GHSA-6676-cqfm-gw84, 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 GHSA-6676-cqfm-gw84 published, and has it been updated?

GHSA-6676-cqfm-gw84 was published on March 6, 2024 and was last updated on September 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 Bitnami

Not in CISA KEV

SQL injection in WordPressGHSA-6676-cqfm-gw84

Fix: WordPress/wordpress-develop@17efac8

GHSA-6676-cqfm-gw84 is a SQL Injection vulnerability in wordpress. 20 public exploit references exist, so weaponization risk is real. A fix is available for wordpress — see the affected versions and patch details below.

Also known asBIT-wordpress-multisite-2022-21661CVE-2022-21661

Published

Mar 6, 2024

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

20 known

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

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-6676-cqfm-gw84.

EPSS Exploitation Probability

via FIRST.org ↗

97.8%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.

Real-World Exposure

1 pkg affected

📦wordpress

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

Description

WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to improper sanitization in WP_Query, there can be cases where SQL injection is possible through plugins or themes that use it in a certain way. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦Bitnami	`wordpress`	≥ 3.7.0&&< 3.7.37	3.7.37

Affected Products

3 products · 27 configurations

debian linuxdebian

3 versions

9.010.011.0

fedorafedoraproject

2 versions

3435

Application

wordpresswordpress

≥ 5.8 && < 5.8.3

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-50663webappsphp

WordPress Core 5.8.2 - 'WP_Query' SQL Injection

by Aryan Chehreghani · Jan 13, 2022

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

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

How to detect GHSA-6676-cqfm-gw84

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

nuclei -id ghsa-6676-cqfm-gw84 -u https://target

Template: WordPress <5.8.3 - SQL Injection
Severity: high
Impact: Successful exploitation of this vulnerability could allow an attacker to execute arbitrary SQL queries, potentially leading to unauthorized access, data manipulation, or data leakage.
Remediation: This has been patched in 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this vulnerability.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-6676-cqfm-gw84 in your dependencies?

Find it across Bitnami, including transitive dependencies.

Scan my dependencies How O3 SCA works