Security Resilience

CVE-2025-26136

SQLi in Wangl1989 Mysiteforme ≤ 2025-01-01

Published
04 March 2025
Modified
24 June 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0040 33th percentile
Risk Priority 71 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-26136 is a critical-severity SQL Injection (CWE-89) vulnerability in Wangl1989 Mysiteforme. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 33th 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.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-26136, published on 2025-03-04, is a SQL injection vulnerability (CWE-89) in mysiteforme versions prior to 2025.01.1. The flaw carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), marking it as critical due to its potential for severe impact across confidentiality, integrity, and availability.

Remote attackers require no authentication privileges or user interaction and can exploit the issue over the network with low attack complexity. Successful exploitation enables arbitrary SQL injection, allowing attackers to read sensitive data, modify database contents, execute administrative operations, or cause denial of service.

The reference advisory at https://gist.github.com/xiadmin6/6d664692d31a04eb59096a488b9f3712 provides details on mitigation, which includes upgrading to mysiteforme version 2025.01.1 or later to address the vulnerability in affected versions.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

A SQL injection vulnerability exists in mysiteforme versions prior to 2025.01.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-10759Shared CWE-89
CVE-2023-41542Shared CWE-89
CVE-2023-3689Shared CWE-89
CVE-2024-3816Shared CWE-89
CVE-2024-10072Shared CWE-89
CVE-2023-35132Shared CWE-89
CVE-2023-26453Shared CWE-89
CVE-2024-30504Shared CWE-89
CVE-2024-39909Shared CWE-89
CVE-2023-3717Shared CWE-89

Affected Assets

wangl1989
mysiteforme
≤ 2025-01-01

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)
  • V6.2.5

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover SQLi flaws before deployment but does not stop their introduction.

Input validation directly stops untrusted data from reaching SQL query construction without neutralization.

Secure engineering principles require parameterized queries and input sanitization that structurally eliminate SQLi.

System monitoring can identify attempted SQLi exploitation via anomalous queries after the weakness exists.

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
blocks

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
blocks

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.

finds

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

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.

finds

created from the owner's anchor; an owner grade is a row and does not wait for an instrument (Mythos 2026-09-29T15:58Z).

References