FortiportalApplication · Fortinet
CVE-2023-46712
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 access control in Fortinet FortiPortal version 7.0.0 through 7.0.6, Fortinet FortiPortal version 7.2.0 through 7.2.1 allows attacker to escalate its privilege via specifically 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 improper access control vulnerability in Fortinet FortiPortal versions 7.0.0-7.0.6 and 7.2.0-7.2.1 that allows authenticated attackers to escalate their privileges via specifically crafted HTTP requests. The vulnerability stems from insufficient validation of user permissions in certain API endpoints, enabling lower-privileged users to perform actions reserved for higher-privileged roles.
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
FortiportalApplication
>= 7.0.0, <= 7.0.6>= 7.2.0, <= 7.2.1CVSS 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 FortiPortal installed versionAccess FortiPortal admin GUI and navigate to System Settings > About, or run 'get system status' via CLI to retrieve the firmware versionAffected if The version number falls within 7.0.0-7.0.6 or 7.2.0-7.2.1
-
Confirm API endpoint accessibilityCheck if FortiPortal API endpoints are reachable from the network by attempting a curl or HTTP request to common API paths such as /api/v1/ or /api/ - verify if management interfaces are exposed to untrusted networksAffected if API endpoints are accessible without additional network restrictions
-
Verify user role configurationReview user accounts and their assigned roles in FortiPortal under User & Authentication > User Groups or similar, noting which users have lower-privileged roles such as Read-Only or standard userAffected if Multiple user roles exist with varying privilege levels, enabling a lower-privileged authenticated user to potentially exploit privilege escalation
-
Inspect API permission enforcementLog in as a lower-privileged user and attempt to access API endpoints reserved for admin or higher-privileged roles using crafted HTTP requests with modified authorization headersAffected if The API accepts and processes requests from lower-privileged users for operations that should require higher permissions
You are affected if FortiPortal runs version 7.0.0-7.0.6 or 7.2.0-7.2.1 and lower-privileged authenticated users can access API endpoints that should be restricted to higher-privileged roles.
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.
dbcve · scopedApply the vendor-supplied patch for FortiPortal 7.0.x and 7.2.x. If no patch is immediately available, restrict network access to FortiPortal management interfaces to trusted IPs and implement additional authentication controls on affected endpoints.
FortiPortal 7.0.7+ or 7.2.2+ or latest 7.4.x stable
- 1. Identify the current FortiPortal version by checking the FortiPortal admin UI or running: 'fortiportal -v' or checking the system information page
- 2. If running version 7.0.0-7.0.6, upgrade to version 7.0.7 or later in the 7.0.x branch
- 3. If running version 7.2.0-7.2.1, upgrade to version 7.2.2 or later in the 7.2.x branch
- 4. Alternatively, upgrade to the latest stable 7.4.x branch which is not affected by this vulnerability
- 5. After upgrade, verify the new version is running: 'fortiportal -v'
- 6. Test that normal authentication and authorization flows work correctly
- 7. Confirm privilege escalation is no longer possible by reviewing FortiGuard release notes for the upgrade version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiportal
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-2023-46712 — 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-2023-46712 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