CVE-2025-56556VulnerabilityPublished 11 Sep 2025Updated 25 Nov 2025

CVE-2025-56556: n/a

Source CVE Database V5

Not known to be exploited · CVSS 3.8 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.8Low

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 11 Sep 2025
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 2026-10-26.

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 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

AI-suggested

1. Restrict access to the SQL Tool admin panel strictly to trusted administrators and minimize the number of users with access to the Run SQL Query feature. 2. Implement strong authentication and authorization controls, including multi-factor authentication for admin and moderator accounts. 3. Regularly audit user roles and permissions to ensure that only necessary privileges are assigned. 4. Monitor and log all SQL queries executed via the admin panel to detect suspicious or unauthorized activities promptly. 5. Apply vendor patches or updates as soon as they become available to address this vulnerability directly. 6. Consider isolating the CMS environment and database access to reduce the blast radius in case of exploitation. 7. Educate administrators and moderators about the risks of misuse of the SQL query feature and enforce strict operational procedures.

Description

CVE-2025-56556 is a vulnerability in Subrion CMS 4.2.1 that allows authenticated administrators or moderators with access to the built-in Run SQL Query feature to escalate privileges within the SQL query tool context. The flaw requires authenticated access with high privileges but does not require user interaction. The vulnerability impacts confidentiality and integrity but not availability, with a CVSS score of 3.8 indicating low severity. No known exploits are currently reported in the wild. European organizations using Subrion CMS 4.2.1, especially those with multiple admin or moderator roles, should be aware of this risk.

Impact

For European organizations using Subrion CMS 4.2.1, this vulnerability poses a risk of privilege escalation for users who already have elevated roles such as administrators or moderators. While the initial access requires high privileges, the flaw could allow these users to perform unauthorized SQL queries that may lead to unauthorized data access or modification, impacting data confidentiality and integrity. This could be particularly damaging for organizations handling sensitive personal data under GDPR, as unauthorized data manipulation or leakage could lead to compliance violations and reputational damage. Although availability is not impacted, the integrity compromise could affect business operations relying on accurate database information. The risk is mitigated by the requirement for authenticated access, but insider threats or compromised accounts could exploit this vulnerability. The absence of known exploits reduces immediate risk but does not eliminate the potential for future exploitation.

CWE-566Authorization Bypass Through User-Controlled SQL Primary Key (opens in a new tab)
Variant weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses a database table that includes records that should not be accessible to an actor, but it executes a SQL statement with a primary key that can be controlled by that actor.
Implementation
Assume all input is malicious. Use a standard input validation mechanism to validate all input for length, type, syntax, and business rules before accepting the data. Use an "accept known good" validation strategy.
Implementation
Use a parameterized query AND make sure that the accepted values conform to the business rules. Construct your SQL statement accordingly.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/intelliants/subrion/issues/913 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 2 Dec 2025, 14:53 UTC

WeaknessesCWE-566

Technical details

References

Community reviews

Related threats