FortipamOperating system · Fortinet
CVE-2025-22256
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an access control vulnerability in FortiPAM and FortiSRA where the system improperly handles permission checks, allowing authenticated attackers to bypass privilege boundaries via specially crafted HTTP requests. The vulnerability enables improper access to resources or functions that should be restricted based on user privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortipamOperating system
>= 1.0.0, < 1.0.4>= 1.1.0, < 1.1.3>= 1.4.0, < 1.4.2= 1.2.0= 1.3.0
FortisraApplication
>= 1.4.0, < 1.4.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed FortiPAM or FortiSRA versionLog into the Forti device CLI and run: get system status or FortiPAM/FortiSRA web UI under System > Settings > Firmware versionAffected if The displayed version falls within these ranges: FortiPAM 1.0.0-1.0.3, 1.1.0-1.3.2, 1.4.0-1.4.1, or specifically 1.2.0 or 1.3.0; FortiSRA 1.4.0-1.4.1
-
Confirm product type is vulnerableFrom the version output in step 1, confirm whether the device is FortiPAM or FortiSRAAffected if The device is FortiPAM any version listed in step 1, or FortiSRA version 1.4.0 to 1.4.1
-
Verify web management interface is accessibleAttempt to access the FortiPAM/FortiSRA web UI via HTTPS on port 443 or check if the management interface is exposed to networkAffected if The web interface is reachable from network segments where untrusted users could send HTTP/HTTPS requests
-
Review access logs for anomalous HTTP requestsCheck FortiPAM/FortiSRA logs under Log & Report > Event Log for unusual API calls or privilege escalation attempts, particularly patterns involving modified HTTP headers or parametersAffected if Logs show HTTP requests that bypassed normal permission checks or accessed privileged endpoints from standard user accounts
If the device runs FortiPAM version 1.0.0-1.0.3, 1.1.0-1.3.2, 1.4.0-1.4.1, 1.2.0, or 1.3.0, or FortiSRA version 1.4.0-1.4.1, and the web interface is network-accessible, the environment is likely affected by this access control bypass vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.41.1.31.4.2
Apply the vendor-supplied patches for the affected FortiPAM and FortiSRA versions. In the interim, restrict administrative interface access to trusted IP ranges only and monitor for anomalous HTTP request patterns.
Fix this in Fortipam
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22256 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22256 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data