How severe is CVE-2021-43091?

CVE-2021-43091 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2021-43091?

CVE-2021-43091 affects the following packages: yeswiki/yeswiki (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-43091?

Update yeswiki/yeswiki to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-43091 is resolved across your whole dependency graph.

How do I detect CVE-2021-43091 in my Packagist dependencies?

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

How do I mitigate CVE-2021-43091 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-2021-43091 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2021-43091, including 1 in-the-wild exploitation 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-2021-43091?

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

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

CVE-2021-43091 was published on March 25, 2022 and was last updated on October 20, 2026. 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

HIGH severity

CVE-2021-43091 — yeswiki

HIGHFix: yeswiki/yeswiki@c9785f9

CVE-2021-43091 is a high-severity (CVSS 7.5) SQL Injection vulnerability in yeswiki/yeswiki. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for yeswiki/yeswiki — see the affected versions and patch details below.

SQL Injection in Yeswiki

Also known asGHSA-xgx2-332h-9x6q

Published

Mar 25, 2022

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

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

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% 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

🐘yeswiki/yeswiki

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

An SQL Injection vlnerability exits in Yeswiki doryphore 20211012 via the email parameter in the registration form. The issue was fixed in Yeswiki version 4.1.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`yeswiki/yeswiki`	all versions	4.1.0`composer require yeswiki/yeswiki:^4.1.0`

Affected Products

1 product · 1 configurations

Application

yeswikiyeswiki

1 version

4.1.0

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.

An SQL Injection vlnerability exits in Yeswiki doryphore 20211012 via th…

huntr.devNVDMar 2022

Detection & mitigation playbook

Open-source dependency

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

An SQL Injection vlnerability exits in Yeswiki doryphore 20211012 via the email parameter in the registration form. The issue was fixed in Yeswiki version 4.1.0.

O3 Security · Impact-Aware SCA

Is CVE-2021-43091 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Mar 25, 2022

First exploit

Mar 29, 2022

4 days after disclosure — rapid exploitation

Last updated

Oct 20, 2026

Identifiers

CVE-2021-43091

GHSA-xgx2-332h-9x6q

References

Advisorynvd.nist.gov · CVE 2021 43091 Fixgithub.com · c9785f9a92744c3475f9676a0d8f95de24750094 Fixhuntr.dev · 07f245a7 ee9f 4b55 a0cc 13d5cb1be6e0 Webhuntr.dev · 07f245a7 ee9f 4b55 a0cc 13d5cb1be6e0 Packagegithub.com · yeswiki

Related vulnerabilities

This CVE is high severity; 6 of 8 other CVEs affecting yeswiki/yeswiki are rated as high or higher (top: critical).

CVE-2026-52773CVE-2026-52775CVE-2026-52762CVE-2026-52766CVE-2026-52763CVE-2026-52771CVE-2026-52777CVE-2026-52767

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026

CVE-2021-43091 — yeswiki

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-43091 in your dependencies?