Taxonomy metadata modification via missing nonce validation
Published Feb 27, 2024 · Updated Apr 8, 2026
CSRF in Frenify Categorify 1.0.7.4 and earlier allows remote attackers to alter category positions and taxonomy metadata. The categorifyAjaxUpdateFolderPosition handler accepts a forged state-changing request without valid nonce verification and writes the supplied folder ordering and taxonomy metadata. Exploitation requires an administrator with an active session to perform an attacker-induced action, such as opening a crafted link.
Summary
What happened
CSRF in Frenify Categorify 1.0.7.4 and earlier allows remote attackers to alter category positions and taxonomy metadata. The categorifyAjaxUpdateFolderPosition handler accepts a forged state-changing request without valid nonce verification and writes the supplied folder ordering and taxonomy metadata. Exploitation requires an administrator with an active session to perform an attacker-induced action, such as opening a crafted link.
The record
- CVE
- CVE-2024-1912
- Published
- Feb 27, 2024
- Updated
- Apr 8, 2026
- Vendor
- Frenify
- Product
- Categorify
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 27, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.0.7.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo