VulnerabilityPublished 1 Nov 2024Updated 4 Nov 2024

CVE-2024-40490: sourcebans-pp · Observable Discrepancy

Affects sourcebans-ppSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 1.8.0 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.8.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade sbpp/sourcebans-pp to 1.8.0.

Affected software

Product	Affected	Fixed in
GitHubsbpp/sourcebans-pp`pkg:github/sbpp/sourcebans-pp`Other threats	Affected <1.8.0	Fixed in 1.8.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Sourcebans++ to version 1.8.0 or later as soon as the patch is released to address the vulnerability directly.
If you cannot patch yet, restrict access to the Forgot Password functionality by implementing IP whitelisting or network segmentation to limit exposure.
Employ web application firewalls (WAFs) with custom rules to detect and block suspicious or malformed XAJAX requests targeting the Forgot Password endpoint.
Monitor server logs for unusual activity related to password reset requests, especially those with abnormal parameters or originating from unknown IP addresses.
Conduct regular security assessments and code reviews focusing on access control mechanisms in web application components.
Educate administrators and users about the risks of phishing and social engineering that may arise from leaked sensitive information.
Implement multi-factor authentication (MFA) for administrative access to reduce the impact of potential credential compromise.
Maintain an incident response plan to quickly address any detected exploitation attempts or data breaches related to this vulnerability.

Description

An issue in Sourcebans++ before v.1.8.0 allows a remote attacker to obtain sensitive information via a crafted XAJAX call to the Forgot Password function.

Impact

The primary impact of CVE-2024-40490 is the unauthorized disclosure of sensitive information, which can include user account details or other confidential data managed by Sourcebans++. This breach of confidentiality can lead to further attacks such as targeted phishing, account takeover, or social engineering against administrators and users of the affected gaming servers. Since the vulnerability does not affect integrity or availability, it does not directly enable data modification or service disruption. However, the ease of remote exploitation without authentication or user interaction increases the likelihood of attacks, especially in environments where Sourcebans++ is exposed to the internet. Organizations operating gaming servers or communities that rely on Sourcebans++ for ban management may face reputational damage, loss of user trust, and potential compliance issues if sensitive user data is leaked. The lack of known exploits in the wild currently reduces immediate risk, but the vulnerability's characteristics warrant proactive mitigation to prevent future exploitation.

CWE-203Observable Discrepancy (opens in a new tab)
Base weakness
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Black Box Reverse Engineering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/sbpp/sourcebans-pp/issues/975 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 05:23 UTC

WeaknessesCWE-203

Technical details

References

Community reviews

Related threats