CVE-2026-28226
Authenticated SQL Injection in Phishing Club GetOrphaned Endpoint
Publication date: 2026-02-26
Last updated on: 2026-03-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| phishing.club | phishing_club | to 1.30.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Phishing Club, a phishing simulation and man-in-the-middle framework, in versions prior to 1.30.2. It is an authenticated SQL injection vulnerability found in the GetOrphaned recipient listing endpoint. The issue arises because the endpoint constructs a raw SQL query and directly concatenates a user-controlled parameter called sortBy into the ORDER BY clause without validating it against an allowlist. Unknown values are silently passed through a function called RemapOrderBy(), allowing an authenticated attacker to inject malicious SQL expressions into the ORDER BY clause. This vulnerability was fixed in version 1.30.2 by implementing validation of the order-by column against an allowlist and clearing unknown mappings.
How can this vulnerability impact me? :
This vulnerability allows an authenticated attacker to perform SQL injection attacks via the ORDER BY clause in the GetOrphaned recipient listing endpoint. The CVSS score of 6.5 indicates a medium severity impact with high confidentiality impact but no impact on integrity or availability. This means an attacker could potentially access sensitive data from the database without altering or disrupting the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Phishing Club to version 1.30.2 or later, where the issue has been patched by validating the order-by column against an allowlist and clearing unknown mappings.