LiveActive security incident?Get immediate response
CVE Record

CVE-2013-10035: ProcessMaker Open Source < 2.5.2 neoclassic Skin PHP Code Execution

A code injection vulnerability exists in ProcessMaker Open Source versions 2.x when using the default 'neoclassic' skin. An authenticated user can execute arbitrary PHP code via multiple endpoints, including appFolderAjax.php, casesStartPage_Ajax.php, and cases_SchedulerGetPlugins.php, by supplying crafted POST requests to parameters such as action and params. These endpoints fail to validate user input and directly invoke PHP functions like system() with user-supplied parameters, enabling remote code execution. The vulnerability affects both Linux and Windows installations and is present in default configurations of versions including 2.0.23 through 2.5.1. The vulnerable skin cannot be removed through the web interface, and exploitation requires only valid user credentials.

HighCVSS 8.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

ProcessMaker Open Source 2.x installations using the default neoclassic skin can let any authenticated user run PHP code on the server. That can mean full compromise of the workflow system and its hosted data. The record does not show CISA KEV listing or confirmed active exploitation, but public exploit references exist.

Executive priority

Treat this as urgent for any legacy ProcessMaker system. It is authenticated, but successful exploitation can give server-level code execution. Prioritize patching or isolating affected deployments, especially if externally reachable or used by many business users.

Technical view

The flaw is CWE-94 code injection in neoclassic skin endpoints including appFolderAjax.php, casesStartPage_Ajax.php, and cases_SchedulerGetPlugins.php. User-controlled POST parameters are passed into PHP function invocation paths, enabling authenticated remote code execution on Linux and Windows. Sources describe affected versions through 2.5.1 and a fix in 2.5.2.

Likely exposure

Exposure is most likely in legacy ProcessMaker Open Source 2.x deployments, especially versions 2.0.23 through 2.5.1 using the default neoclassic skin. Internet-facing workflow portals and broadly provisioned internal user accounts increase risk.

Exploitation context

Exploitation requires valid ProcessMaker credentials, but no user interaction beyond the authenticated request. Public exploit references are cited by the source bundle. KEV is false, and the supplied sources do not establish active exploitation in the wild.

Researcher notes

Affected-version metadata in the bundle is sparse, but the description and advisories identify ProcessMaker Open Source before 2.5.2. Avoid assuming exploitation beyond public exploit availability. Focus validation on version, neoclassic skin presence, endpoint exposure, and authenticated abuse indicators.

Mitigation direction

  • Upgrade ProcessMaker Open Source to 2.5.2 or later where applicable.
  • Restrict ProcessMaker access to trusted networks or VPN users.
  • Audit and remove unnecessary ProcessMaker user accounts.
  • Monitor vendor guidance before making compensating changes.
  • Prioritize replacement of unsupported legacy ProcessMaker 2.x systems.

Validation and detection

  • Inventory all ProcessMaker Open Source deployments and versions.
  • Confirm whether the neoclassic skin is present and active.
  • Review access logs for POST activity to the cited endpoints.
  • Check authentication logs for unusual low-privilege user activity.
  • Validate remediation in staging before production rollout.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-10035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.7 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.7CVSS 4.0HighCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——VulnCheck

Vulnerability scoring details

Base CVSS 4.0 score

8.7High
CVSS 4.0 vector shape for CVE-2013-10035Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ProcessMaker, Inc.ProcessMaker Open Source2.0unaffected
Weakness

CWE details

CWE-94

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs