Skip to main content
No exploitation reportedFix available

CVE-2017-16244

No exploitation reported by the sources we read.

  • Published2017-11-01
  • WeaknessCWE-352

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Cross-Site Request Forgery exists in OctoberCMS 1.0.426 (aka Build 426) due to improper validation of CSRF tokens for postback handling, allowing an attacker to successfully take over the victim's account. The attack bypasses a protection mechanism involving X-CSRF headers and CSRF tokens via a certain _handler postback variable.

Timeline

dates in UTC
  1. 2017-11-0101:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-16244?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-16244?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Octobercms october
BranchAffectedFixed in
1.0= 1.0.426no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.08.8read 2026-10-23
  • NVDCVSS 2.06.8read 2026-10-23
  • NVDweakness (CWE)CWE-352read 2026-10-23
  • FIRST EPSSEPSS score2.0 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published
2017-11-01
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2017-16244?

Cross-Site Request Forgery exists in OctoberCMS 1.0.426 (aka Build 426) due to improper validation of CSRF tokens for postback handling, allowing an attacker to successfully take over the victim's account. The attack bypasses a protection mechanism involving X-CSRF headers and CSRF tokens via a certain _handler postback variable.

Is CVE-2017-16244 actively exploited?

Active exploitation of CVE-2017-16244 has not been confirmed. Its EPSS score was 2.0% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-16244?

CVE-2017-16244 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month