{
  "id": "CVE-2026-80210",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-80210",
  "published_at": "2026-08-27T14:50:31.106Z",
  "title": "FrontAccounting through 2.4.20 Cross-Site Request Forgery on Financial Transaction Forms",
  "vendor": "FrontAccounting",
  "product": "FrontAccounting",
  "cvss": {
    "score": 7.1,
    "source": "cna",
    "vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N"
  },
  "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": null,
  "description": "FrontAccounting through 2.4.20 generates a CSRF token in end_form() in includes/ui/ui_controls.inc and embeds it as the _token hidden field in every form it renders, but only admin/users.php and admin/change_current_user_password.php call check_csrf_token() to validate it. No financial transaction handler validates the token, including gl/gl_journal.php, gl/gl_bank.php, purchasing/supplier_invoice.php, sales/customer_invoice.php, sales/customer_payments.php and admin/company_preferences.php, so those endpoints act on POST data with no origin check. An attacker who gets an authenticated user to load a page under attacker control can auto-submit a cross-origin form to any of them and have the forged journal entry, invoice, customer payment, bank transaction or company configuration change recorded under the victim's session.",
  "cwe": "CWE-352",
  "cvss_by_source": {
    "cna": 7.1
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "FrontAccounting",
        "product": "FrontAccounting",
        "ranges": [
          "\u003c= 2.4.20"
        ],
        "fixed_in": null
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
