Skip to main content
CVE-2025-22256VulnerabilityPublished

CVE-2025-22256: Fortinet FortiPAM · Improper access control

Affects Fortinet FortiPAMSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:U/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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-25.

What to do

Affected software

ProductAffectedFixed in
Fortinet FortiPAMAffected
  • =1.4.0
  • =1.3.0
  • =1.2.0
  • =1.1.0
  • =1.0.0
Fixed in–

AI-suggested

European organizations should prioritize the following mitigation steps: 1) Immediately inventory and identify all FortiPAM and FortiSRA instances in their environment, including version numbers, to assess exposure. 2) Monitor Fortinet's official channels for patches or security advisories addressing CVE-2025-22256 and apply updates promptly once available. 3) Implement strict network segmentation and access controls to limit administrative access to FortiPAM interfaces, restricting access to trusted management networks only. 4) Enforce multi-factor authentication (MFA) for all privileged accounts interacting with FortiPAM to reduce the risk of credential misuse. 5) Conduct thorough logging and monitoring of FortiPAM access and administrative actions to detect anomalous behavior indicative of exploitation attempts. 6) Review and tighten permission assignments within FortiPAM to ensure the principle of least privilege is enforced, minimizing the impact of compromised accounts. 7) Consider deploying web application firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block suspicious HTTP requests targeting FortiPAM. These targeted mitigations go beyond generic advice by focusing on access restriction, monitoring, and rapid patch management tailored to the nature of this vulnerability.

Description

A improper handling of insufficient permissions or privileges in Fortinet FortiPAM 1.4.0 through 1.4.1, 1.3.0, 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiSRA 1.4.0 through 1.4.1 allows attacker to improper access control via specially crafted HTTP requests

References

Community reviews

Loading reviews…