Cyber Resilience

CVE-2024-13263

Opigno Group Manager ≤ 3.1.1

Published
09 January 2025
Modified
27 August 2025
CVSS Score v3.1 5.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
EPSS Score 0.0026 18th percentile
Risk Priority 42 floored blend · peak EPSS

Summary

CVE-2024-13263 is a medium-severity Static Code Injection (CWE-96) vulnerability in Opigno Group Manager. Its CVSS base score is 5.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') vulnerability in Drupal Opigno group manager allows PHP Local File Inclusion.This issue affects Opigno group manager: from 0.0.0 before 3.1.1.

CWE(s)
CWE-96

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1027.009 Embedded Payloads Stealth
Adversaries may embed payloads within other files to conceal malicious content from defenses.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-13264Same vendor: Opigno
CVE-2024-13267Same vendor: Opigno
CVE-2024-13268Same vendor: Opigno
CVE-2024-13265Same vendor: Opigno
CVE-2025-57707Shared CWE-96
CVE-2025-36595Shared CWE-96
CVE-2024-0788Shared CWE-96
CVE-2024-32487Shared CWE-96
CVE-2025-7825Shared CWE-96
CVE-2023-39726Shared CWE-96

Affected Assets

opigno
group manager
≤ 3.1.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.

SI-10 Information Input Validation good match

Input validation directly stops unneutralized directives from being inserted into static code resources.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization to block static code injection into templates, configs, or libraries.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance will detect static code injection but does not prevent it at the source.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents static code injection.

A.8.26 Application security requirements partial match
prevents

Application security requirements include rules for neutralizing untrusted input before it is stored in executable resources.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe the specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.

A.8.32 Change management none match
mitigates

Change management can catch unsafe code changes but does not enforce input neutralization.

References