Cyber Resilience

CVE-2025-62423

SQLi in Oxygenz Clipbucket 5.3 – 5.5.2-142

Public PoCSQLi
Published
16 October 2025
Modified
10 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 6.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L
EPSS Score 0.0048 39th percentile
Risk Priority 43 floored blend · peak EPSS

Summary

CVE-2025-62423 is a medium-severity SQL Injection (CWE-89) vulnerability in Oxygenz Clipbucket. Its CVSS base score is 6.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and AC-6 (Least Privilege) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

ClipBucket V5 provides open source video hosting with PHP. In version5.5.2 - #140 and earlier, a Blind SQL injection vulnerability exists in the Admin Area’s “/admin_area/login_as_user.php” file. Exploiting this vulnerability requires access privileges to the Admin Area.

CWE(s)
CWE-89

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

Blind SQL injection in a web-accessible admin script (login_as_user.php) directly enables exploitation of a public-facing web application (T1190) via crafted input to a database query.

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2024-0890Shared CWE-89
CVE-2024-25168Shared CWE-89
CVE-2024-5063Shared CWE-89
CVE-2024-27289Shared CWE-89
CVE-2024-33404Shared CWE-89
CVE-2024-31547Shared CWE-89
CVE-2024-34987Shared CWE-89
CVE-2024-7853Shared CWE-89
CVE-2024-6966Shared CWE-89
CVE-2024-30872Shared CWE-89

Affected Assets

oxygenz
clipbucket
5.3 — 5.5.2-142

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.2.5

Mitigating Controls (NIST 800-53 r5) AI

SI-10 Information Input Validation good match
prevent

Directly requires validation and sanitization of all inputs to the login_as_user.php endpoint, blocking the malicious SQL payload before it reaches the database.

AC-6 Least Privilege partial match
prevent

Restricts the number of accounts permitted to reach the Admin Area, thereby reducing the population that can exploit the blind SQLi in login_as_user.php.

SI-4 System Monitoring partial match
detect

Enables monitoring of database query patterns and anomalies originating from admin scripts, allowing detection of attempted or successful blind SQL 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 target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.

PR.AT-02 partial match
prevents

Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.

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
detects

The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.

A.5.6 Contact with special interest groups partial match
prevents

Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.

A.5.7 Threat intelligence partial match
prevents

Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.

A.8.25 Secure development life cycle partial match
prevents

Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.

A.8.28 Secure coding partial match
prevents

Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.

References