CVE-2024-44546: PowerJob · SQL Injection
Affects PowerJobSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpowerjob/PowerJobpkg:github/powerjob/PowerJobOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, organizations should prioritize the following actions: 1) Monitor official Powerjob channels for security advisories and apply patches immediately once available. 2) Implement strict input validation and sanitization on all parameters, especially the 'version' parameter, to prevent injection attacks. 3) Deploy Web Application Firewalls (WAFs) with rules designed to detect and block SQL injection attempts targeting Powerjob endpoints. 4) Restrict network access to Powerjob management interfaces, limiting exposure to trusted internal networks or VPNs. 5) Conduct thorough security assessments and penetration testing focused on injection vulnerabilities within Powerjob deployments. 6) Employ database security best practices such as least privilege access, query parameterization, and regular auditing to minimize impact if exploitation occurs. 7) Maintain comprehensive logging and monitoring to detect suspicious activities promptly. These measures collectively reduce the attack surface and improve resilience against exploitation until official patches are applied.
Description
Powerjob >= 3.20 is vulnerable to SQL injection via the version parameter.