CVE-2025-31284VulnerabilityPublished 2 Apr 2025Updated 26 Feb 2026

CVE-2025-31284: Trend Vision One · Improper Privilege Mangement

Affects Trend Vision OneSource CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.6Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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 2 Apr 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

Organizations should verify that their Trend Vision One deployments are running the latest backend service versions where this vulnerability has been addressed. Conduct thorough audits of user roles and permissions within Trend Vision One to ensure no unauthorized privilege escalations are possible. Implement strict administrative access controls and monitor administrative activities for suspicious behavior. Employ multi-factor authentication for all administrative accounts to reduce risk of credential compromise. Regularly review and update security policies related to user management in Trend Vision One. If possible, isolate the Trend Vision One management interface to trusted networks and restrict access via network segmentation and firewall rules. Maintain up-to-date incident response plans to quickly detect and respond to any suspicious privilege escalations. Engage with Trend Micro support for any additional patches or guidance related to this vulnerability.

Description

A broken access control vulnerability previously discovered in the Trend Vision One Status component could have allowed an administrator to create users who could then change the role of the account and ultimately escalate privileges. Please note: ths issue has already been addressed on the backend service and is no longer considered an active vulnerability.

Impact

If exploited, this vulnerability could allow an attacker with administrative access to escalate privileges by altering user roles, potentially gaining unauthorized control over security monitoring and management functions. This could lead to manipulation or suppression of security alerts, unauthorized access to sensitive data, and disruption of incident response activities. Although exploitation requires initial admin privileges, the ability to escalate privileges undermines the principle of least privilege and could facilitate further attacks within the network. Organizations relying on Trend Vision One for centralized security operations could face increased risk of insider threats or lateral movement by attackers. The absence of known exploits and backend remediation reduces immediate risk, but unpatched or misconfigured deployments remain vulnerable. The medium severity rating reflects moderate impact on confidentiality and integrity, with no direct availability impact.

Summary

CVE-2025-31284 is a vulnerability classified under CWE-269 (Improper Privilege Management) found in Trend Micro's Trend Vision One security platform. The flaw existed in the Status component, where an administrator could create new user accounts that were capable of modifying their own roles, effectively escalating their privileges beyond intended limits. This broken access control issue could allow attackers with initial administrative access to expand their control within the system, potentially compromising confidentiality and integrity of security monitoring data. The vulnerability requires an attacker to have administrative privileges initially and involves user interaction, which reduces the likelihood of remote exploitation by unauthorized users. The CVSS v3.1 base score is 4.6, indicating medium severity, with attack vector network-based, low attack complexity, privileges required, and user interaction needed. The vulnerability has been remediated by backend service updates, and no active exploits have been reported. Trend Vision One is a widely used security operations platform, so the vulnerability could have significant implications if exploited in unpatched environments.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

success.trendmicro.com/en-US/solution/KA-0019386 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Feb 2026, 20:05 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats