CVE-2023-52137Disclosure(tj-actions / verify-changed-files)

LOWCVSS 8.8 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

The [`tj-actions/verify-changed-files`](https://github.com/tj-actions/verify-changed-files) action allows for command injection in changed filenames, allowing an attacker to execute arbitrary code and potentially leak secrets. The [`verify-changed-files`](https://github.com/tj-actions/verify-changed-files) workflow returns the list of files changed within a workflow execution. This could potentially allow filenames that contain special characters such as `;` which can be used by an attacker to take over the [GitHub Runner](https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners) if the output value is used in a raw fashion (thus being directly replaced before execution) inside a `run` block. By running custom commands, an attacker may be able to steal secrets such as `GITHUB_TOKEN` if triggered on other events than `pull_request`. This has been patched in versions [17](https://github.com/tj-actions/verify-changed-files/releases/tag/v17) and [17.0.0](https://github.com/tj-actions/verify-changed-files/releases/tag/v17.0.0) by enabling `safe_output` by default and returning filename paths escaping special characters for bash environments.

0.0/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-20CWE-77

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • verify-changed-files

Threat summary

  • 1 mentions across 1 observed day

What's happening

  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
verify-changed-files

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-05-29: 1Technical Details · 2026-05-29: 105-29
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • sarthak@sar_path
    Disclosure

    1. CVE-2023-52137 (SQL Injection) Description: The application is vulnerable to SQL injection through the 'id' parameter in multiple endpoints. Impact: Allows attackers to extract sensitive data from the database. https://cbseosm.onmark.co.in/cbse_dashboard @ni5arga @NSO365

    Post summary

    CVE-2023-52137 is disclosed as a SQL injection flaw that lets attackers read sensitive data from the database by abusing the 'id' parameter.

    0000076
    72 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Apptj-actionsverify-changed-files-github-

Explore more