Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Targeted enterprise software

What Is Epicor Kinetic? ERP Security, BPM Directives and Attacks

An ERP system that compiles business-rule code by design. Why that makes its database a target, and how defenders can tell admin work from abuse.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
6 min read
Type
Enterprise software (ERP)

In short

Epicor Kinetic is an enterprise resource planning (ERP) platform from Epicor. Its Business Process Management (BPM) feature lets administrators attach custom C# code to business actions. Kinetic stores these hooks in a SQL table and compiles them when the action runs. That makes write access to its database a path to running code on the ERP server.

Key takeaways

What it is
An ERP platform from Epicor, run on Microsoft SQL Server and IIS in the deployment Odin Research describes, with BPM directives that hold custom C# code.
Why it is a target
Anyone who can write to the directive table can place code inside the ERP application server, where endpoint tools rarely look.
Public CVEs
NVD listed no CVE naming Epicor Kinetic on 21 November 2026. Other Epicor products, such as HCM and Prophet 21, have critical and high SQL injection CVEs.
What Odin Research saw
A mirrored four-server cluster staging Epicor directive injection scripts and SQL Server Agent tunnel jobs. A saved reply shows one upload was rejected.
What to do first
Audit writes to the directive table, restrict SQL Server Agent CmdExec steps and keep xp_cmdshell disabled.

What is Epicor Kinetic?

Epicor Kinetic is an enterprise resource planning (ERP) platform from Epicor. It runs core business processes such as orders, inventory and finance. Its Business Process Management (BPM) feature lets administrators attach custom C# code to business actions, so the ERP can enforce company-specific rules.

That flexibility is the security story. According to Odin Research's Monograph 05, Kinetic stores BPM hooks in a SQL table called Ice.BpDirective. When a business method runs, Kinetic compiles and runs the C# custom actions attached to it.

So whoever can write to that table can place code inside the ERP application server. No file upload or classic web shell is needed. The code lives in the database and runs with the ERP's own rights.

Epicor's own technical documentation for BPM is largely behind a customer login. This page relies on Odin Research's analysis and on public Microsoft and MITRE material for the SQL Server side.

How Epicor Kinetic BPM directives work

A directive is a rule tied to a business method, for example an update to a record. Monograph 05 describes the key fields an attacker would care about:

  • The method. Which business object call triggers the directive, such as an Update method in the Ice or Erp namespaces.
  • The source. Directives built in the Workflow Designer normally carry a source of BO or UI. Data directives may also use DB.
  • The action. A custom code action holds C# that Kinetic compiles and runs.

In normal use, administrators build directives in Kinetic's own tools. The risk appears when someone writes rows straight into the table through SQL. MITRE ATT&CK describes a close cousin of this pattern as SQL Stored Procedures (T1505.001): abusing saved database code to keep access to database servers.

Kinetic usually sits on Microsoft SQL Server. That brings SQL Server features into scope too, such as xp_cmdshell and SQL Server Agent jobs.

Epicor Kinetic vulnerabilities and CVEs

A search of the US National Vulnerability Database on 21 November 2026 returned no CVE that names Epicor Kinetic. That does not mean Kinetic is flawless. It means the abuse path in this page is a design feature used with stolen or misused database access, not a patchable bug.

Other Epicor products do have public CVEs. Two recent examples:

  • CVE-2025-22953: SQL injection in the JsonFetcher.svc endpoint of Epicor HCM 2021 1.9 (CVSS 3.1 score 9.8). NVD notes it may lead to remote code execution if features such as xp_cmdshell are enabled.
  • CVE-2024-42844: authenticated SQL injection in Epicor Prophet 21 up to 23.2.5232 (CVSS 3.1 score 8.1).

The common thread is the database. In Epicor products, as in many ERP systems, SQL access is close to code access.

How attackers target Epicor Kinetic

Monograph 05 describes a staged toolkit in four steps. These are files on attacker servers, not a record of a successful intrusion.

  1. Learn the schema. Scripts read the directive, method and server settings tables and return results inside SQL error messages.
  2. Inject a directive. A script inserts a directive with a DB source on an update method. Its custom code writes a marker file into the web server folder. A tiny page checks whether that worked.
  3. Persist through SQL Server Agent. Instead of a shell, scripts create Agent jobs with the CmdExec subsystem to start a tunnel program and download another binary.
  4. Query the domain. A last script makes SQL Server query Active Directory through a linked server, so user lists come back as normal SQL results.

The point of this design is stealth. ERP and database servers do this kind of work every day. A directive change or an Agent job can look like routine admin activity, and workstation endpoint tools rarely watch these systems.

What Odin Research observed

  • A mirrored cluster. Four adjacent servers carried the same 544-path directory tree, 2,176 entries in all, plus a relay that the scripts call. Most entries were seen on 13 November 2026.
  • Twelve injector files per server. Directive injection scripts made up 2.0% of the tree. Odin analyzed 40 SQL, JSON and ASPX files from the first node.
  • Learning from errors. A saved reply shows the operator's first upload was rejected with an "invalid column" error. The operator then staged revised scripts that drop the missing column. No later success reply was found.
  • A training company code. Several scripts use a standard Epicor training company code, which fits testing against a demo tenant or reuse of a template.
  • Domain tooling alongside. The same tree holds Kerberos ticket caches, AS-REP roasting logs and Windows privilege escalation tools such as PrintSpoofer.

Odin Research treats this cluster as adversary staging. The same report covers related toolkits for VMware Cloud Director, n8n and Apache Activiti.

How to detect Epicor Kinetic directive abuse

One signal is never enough, because administrators change directives legitimately. Monograph 05 recommends correlating three:

  1. A DB source on a business object update method.
  2. A custom code action that calls operating-system or file namespaces, such as System.IO, Process or WebClient.
  3. A write by a SQL login that is not the Epicor application-server login.

Treat an unknown SQL login as unknown, not benign. For SQL Server Agent, routine TSQL and SSIS maintenance jobs are fine. Flag CmdExec, PowerShell and ActiveScripting steps, and alert when sqlagent.exe starts programs from unusual folders.

Monograph 05 publishes a Suricata signature (SID 9502601) for directive injection over HTTP and a Sigma rule for SQL Agent droppers and IIS marker files. It also has a YARA rule for Epicor directive injectors and a KQL hunt that includes audited writes to the directive table. All are in the Defense Kit.

How to defend Epicor Kinetic

  1. Audit the directive table. Use SQL Server Audit on Ice.BpDirective and review every change made outside the ERP application login.
  2. Keep xp_cmdshell off. Microsoft says xp_cmdshell is disabled by default on new installations and that new code should not use it.
  3. Restrict SQL Server Agent. Microsoft documents proxies that limit the security context of a job step. Grant CmdExec and PowerShell only to least-privilege proxies.
  4. Remove unneeded linked servers, especially directory providers that let SQL query Active Directory.
  5. Protect database credentials. Anyone with write access to the ERP database can change its behavior. Treat those accounts like domain admin accounts.

Epicor Kinetic compared with other middleware targets

PlatformBuilt-in code pathWhat Monograph 05 found
Epicor KineticBPM directives compile C# custom codeDirective injectors on a mirrored four-server cluster
SQL Server xp_cmdshell and AgentOperating-system commands from the databaseAgent jobs with CmdExec steps that start a tunnel
n8nCode steps inside workflowsAn attacker working folder on a likely victim server
Apache ActivitiGroovy and Spring expressions in workflow modelsModels built to avoid WAF shell strings

Frequently asked questions about Epicor Kinetic

What is Epicor Kinetic?

Epicor Kinetic is an enterprise resource planning (ERP) platform from Epicor. Its BPM feature lets administrators attach custom C# code to business actions, which Kinetic compiles and runs.

Is Epicor Kinetic vulnerable?

NVD listed no CVE naming Epicor Kinetic on 21 November 2026. The main risk Odin Research documents is abuse of its BPM directives by anyone who can write to its SQL database.

What is a BPM directive in Epicor?

A BPM directive is a rule attached to a business method, such as a record update. It can include a custom code action written in C#, which runs when the method is called.

What is the Ice.BpDirective table?

According to Odin Research, it is the SQL Server table where Epicor Kinetic stores BPM directives. Write access to it lets someone place code that runs inside the ERP application server.

How do I detect Epicor directive abuse?

Correlate a DB source on an update method, custom code that calls file or process functions, and a write by a SQL login other than the ERP application login. Odin Research publishes Suricata, Sigma, YARA and KQL rules for this in its Defense Kit.

Which Epicor products have CVEs?

NVD lists CVEs for several Epicor products. Recent examples include CVE-2025-22953, a SQL injection in Epicor HCM, and CVE-2024-42844, an authenticated SQL injection in Epicor Prophet 21.

Should xp_cmdshell be enabled for Epicor?

Microsoft says xp_cmdshell is disabled by default and new code should not use it. If a legacy need exists, Microsoft recommends enabling it only for the duration of the task.

Sources

  1. NVD, CVE API keyword search "Epicor Kinetic". services.nvd.nist.gov/rest/json/cves/2.0?keywordSearch=Epicor%20Kinetic (checked 21 November 2026)
  2. NVD, CVE-2025-22953. nvd.nist.gov/vuln/detail/CVE-2025-22953 (checked 21 November 2026)
  3. NVD, CVE-2024-42844. nvd.nist.gov/vuln/detail/CVE-2024-42844 (checked 21 November 2026)
  4. MITRE ATT&CK, Server Software Component: SQL Stored Procedures, T1505.001. attack.mitre.org/techniques/T1505/001/ (checked 21 November 2026)
  5. Microsoft Learn, Server Configuration: xp_cmdshell. learn.microsoft.com/en-us/sql/database-engine/configure-windows/xp-cmdshell-server-configuration-option (checked 21 November 2026)
  6. Microsoft Learn, Create a SQL Server Agent Proxy. learn.microsoft.com/en-us/ssms/agent/create-a-sql-server-agent-proxy (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit