VulnerabilityPublished 31 Mar 2024Updated 21 Aug 2024

CVE-2024-25979: fedora · Improper Handling of Parameters

Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

5.3Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 31 Mar 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

AI-suggested

To mitigate CVE-2024-25979, organizations should first verify if they are running affected versions (4.3.0, 4.2.0, or 0) of the forum software. Since no official patches are referenced, administrators should implement strict input validation and parameter whitelisting on the forum search endpoint to ensure only allowed parameters are processed. Web application firewalls (WAFs) can be configured to detect and block requests containing unexpected or suspicious URL parameters. Monitoring and logging of search requests should be enhanced to identify abnormal parameter usage patterns. If possible, upgrading to a newer, patched version of the software once available is recommended. Additionally, security teams should conduct regular vulnerability assessments and penetration tests focusing on parameter handling and injection vectors. Educating developers on secure coding practices related to input validation can prevent similar issues in future releases.

Description

The URL parameters accepted by forum search were not limited to the allowed parameters.

Impact

The primary impact of CVE-2024-25979 is a limited confidentiality breach due to improper parameter handling in the forum search functionality. Attackers could potentially craft malicious URLs with unexpected parameters to extract sensitive information or gain insights into the application’s internal workings. However, since there is no impact on integrity or availability, the risk of data manipulation or service disruption is minimal. The vulnerability does not require authentication or user interaction, increasing the attack surface as it can be exploited remotely by any attacker. Organizations running affected versions of the forum software may face information leakage risks, which could aid in further targeted attacks or reconnaissance. The absence of known exploits reduces immediate risk, but the medium severity rating indicates that timely remediation is advisable to prevent future exploitation. The scope is limited to the affected forum software versions and their deployments, which may be significant in communities or enterprises relying on these versions for online discussions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 10:50 UTC

Technical details

References

Community reviews

Related threats