VulnerabilityPublished 7 Feb 2024Updated 9 Jun 2025

CVE-2024-24304: Information Exposure

Source CVE Database V5

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

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

7.5High

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

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

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 7 Feb 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 mailjet/prestashop-mailjet-plugin-apiv3 to 3.5.1.

Affected software

Product	Affected	Fixed in
GitHubmailjet/prestashop-mailjet-plugin-apiv3`pkg:github/mailjet/prestashop-mailjet-plugin-apiv3`Other threats	Affected <3.5.1	Fixed in 3.5.1

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

AI-suggested

European organizations should immediately verify the version of the Mailjet module installed on their PrestaShop platforms and upgrade to version 3.5.1 or later, where the vulnerability is fixed. If immediate upgrade is not feasible, implement access controls at the web server or application firewall level to restrict unauthenticated access to endpoints exposing technical information. Conduct thorough audits of exposed data to identify any leaked credentials or sensitive configuration details and rotate any compromised secrets. Enable detailed logging and monitoring to detect unusual access patterns indicative of exploitation attempts. Additionally, review and harden the overall PrestaShop installation by disabling unnecessary modules and enforcing the principle of least privilege for all components. Regular vulnerability scanning and penetration testing focused on third-party modules like Mailjet should be incorporated into security operations. Finally, maintain awareness of vendor advisories for any subsequent patches or mitigation guidance.

Description

In the module "Mailjet" (mailjet) from Mailjet for PrestaShop before versions 3.5.1, a guest can download technical information without restriction.

Impact

For European organizations operating e-commerce platforms using PrestaShop with the Mailjet module, this vulnerability could lead to unauthorized disclosure of sensitive technical information. Such exposure can facilitate targeted attacks including credential theft, phishing, or further compromise of the e-commerce infrastructure. Confidential customer data might indirectly be at risk if attackers leverage the disclosed information to escalate privileges or access backend systems. This can result in reputational damage, regulatory penalties under GDPR for inadequate data protection, and financial losses due to fraud or downtime. Small and medium enterprises (SMEs) using PrestaShop extensively in Europe may be particularly vulnerable due to limited cybersecurity resources. The impact is heightened in sectors with stringent compliance requirements such as retail, finance, and healthcare e-commerce. Although no direct integrity or availability impact is noted, the confidentiality breach alone is significant given the potential for chained attacks.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
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.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (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
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 21:47 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats