🛡️ CVE-2024-13267 — tincan-question-type

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: High — total loss, or loss the attacker controls.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

CVE-2024-13267 is classified as CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'). The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.

Affected software

CVE-2024-13267 is recorded against 1 package.

• tincan-question-type (from 7.x-1.0 up to 7.x-1.3)

Timeline and source

Published on 9 January 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

www.drupal.org

Same weakness in other software

These advisories are the same class of weakness (CWE-96: Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')) in other software:

• GHSA-5c6j-r48x-rmvq (8.0 High, published 28 Feb 2026)
• CVE-2025-57707 (8.8 High, published 11 Feb 2026)
• CVE-2025-7825 (6.3 Medium, published 3 Oct 2025)
• CVE-2025-36595 (7.2 High, published 27 Jun 2025)
• CVE-2025-30091 (published 25 Mar 2025)
• CVE-2024-13265 (7.5 High, published 9 Jan 2025)
• CVE-2024-13264 (9.8 Critical, published 9 Jan 2025)
• CVE-2024-13263 (5.5 Medium, published 9 Jan 2025)

Details

Affected Packages

References