{
  "id": "CVE-2025-22258",
  "url": "https://poc.griffinguard.io/cve/CVE-2025-22258",
  "published_at": "2025-10-14T15:22:56.72Z",
  "vendor": "Fortinet",
  "product": "FortiPAM",
  "cvss": {
    "score": 7.2,
    "source": "nvd",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": {
    "category": "Firewall / VPN",
    "confidence": "high",
    "reason": "known edge product: fortinet fortiproxy"
  },
  "description": "A heap-based buffer overflow in Fortinet FortiSRA 1.5.0, 1.4.0 through 1.4.2, FortiPAM 1.5.0, 1.4.0 through 1.4.2, 1.3.0 through 1.3.1, 1.2.0, 1.1.0 through 1.1.2, 1.0.0 through 1.0.3, FortiProxy 7.6.0 through 7.6.1, 7.4.0 through 7.4.7, FortiOS 7.6.0 through 7.6.2, 7.4.0 through 7.4.6, 7.2.0 through 7.2.10, 7.0.2 through 7.0.16, FortiSwitchManager 7.2.1 through 7.2.5 allows attackers to escalate their privilege via specially crafted http requests.",
  "cwe": "CWE-122",
  "cpes": [
    "cpe:2.3:a:fortinet:fortiproxy:*:*:*:*:*:*:*:*",
    "cpe:2.3:a:fortinet:fortisra:*:*:*:*:*:*:*:*",
    "cpe:2.3:a:fortinet:fortisra:1.5.0:*:*:*:*:*:*:*",
    "cpe:2.3:a:fortinet:fortiswitchmanager:*:*:*:*:*:*:*:*",
    "cpe:2.3:o:fortinet:fortios:*:*:*:*:*:*:*:*",
    "cpe:2.3:o:fortinet:fortipam:*:*:*:*:*:*:*:*",
    "cpe:2.3:o:fortinet:fortipam:1.5.0:*:*:*:*:*:*:*"
  ],
  "cvss_by_source": {
    "cna": 5.7,
    "nvd": 7.2
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Fortinet",
        "product": "FortiPAM",
        "ranges": [
          "1.5.0",
          "\u003e= 1.4.0, \u003c= 1.4.2",
          "\u003e= 1.3.0, \u003c= 1.3.1",
          "1.2.0",
          "\u003e= 1.1.0, \u003c= 1.1.2",
          "\u003e= 1.0.0, \u003c= 1.0.3"
        ],
        "fixed_in": null
      },
      {
        "vendor": "Fortinet",
        "product": "FortiOS",
        "ranges": [
          "\u003e= 7.6.0, \u003c= 7.6.2",
          "\u003e= 7.4.0, \u003c= 7.4.6",
          "\u003e= 7.2.0, \u003c= 7.2.10",
          "\u003e= 7.0.2, \u003c= 7.0.16"
        ],
        "fixed_in": null
      },
      {
        "vendor": "Fortinet",
        "product": "FortiSRA",
        "ranges": [
          "1.5.0",
          "\u003e= 1.4.0, \u003c= 1.4.2"
        ],
        "fixed_in": null
      },
      {
        "vendor": "Fortinet",
        "product": "FortiProxy",
        "ranges": [
          "\u003e= 7.6.0, \u003c= 7.6.1",
          "\u003e= 7.4.0, \u003c= 7.4.7"
        ],
        "fixed_in": null
      },
      {
        "vendor": "Fortinet",
        "product": "FortiSwitchManager",
        "ranges": [
          "\u003e= 7.2.1, \u003c= 7.2.5"
        ],
        "fixed_in": null
      }
    ],
    "solutions": [
      "Upgrade to FortiPAM version 1.6.0 or above\nUpgrade to FortiPAM version 1.5.1 or above\nUpgrade to FortiPAM version 1.4.3 or above\nFortinet remediated this issue in FortiSASE version 25.1.b and hence customers do not need to perform any action.\nUpgrade to FortiOS version 7.6.3 or above\nUpgrade to FortiOS version 7.4.7 or above\nUpgrade to FortiOS version 7.2.11 or above\nUpgrade to FortiOS version 7.0.17 or above\nUpgrade to FortiSRA version 1.6.0 or above\nUpgrade to FortiSRA version 1.5.1 or above\nUpgrade to FortiSRA version 1.4.3 or above\nUpgrade to FortiProxy version 7.6.2 or above\nUpgrade to FortiProxy version 7.4.8 or above\nUpgrade to FortiSwitchManager version 7.2.6 or above"
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
