CVE-2024-29210

LOWNVD 2.82.8
EchelonGraph scoreMEDIUM confidence

Score 2.8 from GitHub Security Advisory (severity: LOW) published 2024-05-07. NVD baseline CVSS 2.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
2.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A local privilege escalation (LPE) vulnerability has been identified in Phish Alert Button for Outlook (PAB), specifically within its configuration management functionalities. This vulnerability allows a regular user to modify the application's configuration file to redirect update checks to an arbitrary server, which can then be exploited in conjunction with CVE-2024-29209 to execute arbitrary code with elevated privileges.

The issue stems from improper permission settings on the application's configuration file, which is stored in a common directory accessible to all users. This file includes critical parameters, such as the update server URL. By default, the application does not enforce adequate access controls on this file, allowing non-privileged users to modify it without administrative consent.

An attacker with regular user access can alter the update server URL specified in the configuration file to point to a malicious server. When the application performs its next update check, it will contact the attacker-controlled server. If the system is also vulnerable to CVE-2024-29209, the attacker can deliver a malicious update package that, when executed, grants them elevated privileges.

Impact: This vulnerability can lead to a regular user executing code with administrative privileges. This can result in unauthorized access to sensitive data, installation of additional malware, and a full takeover of the affected system.

Affected Products: Phish Alert Button (PAB) for Outlook versions 1.10.0-1.10.11 Second Chance Client versions 2.0.0-2.0.9 PIQ Client versions 1.0.0-1.0.15

Remediation: KnowBe4 has released a patch that corrects the permission settings on the configuration file to prevent unauthorized modifications. Automated updates will be pushed to address this issue. Users of affected versions should verify the latest version is applied and, if not, apply the latest updates provided by KnowBe4.

Workarounds: Manually set the correct permissions on the configuration file to restrict write access to administrators only.

Credits: This vulnerability was discovered by Ceri Coburn at Pen Test Partners, who reported it responsibly to the vendor.

CVSS v3
2.8
EG Score
2.8(medium)
EG Risk
13(Track)
EG Risk 13/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity28% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

May 7, 2024

Last Modified

April 15, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 144 total refreshes for this CVE.

  1. 2026-08-07 16:25 UTCEPSS rescore
  2. 2026-08-06 13:45 UTCEPSS rescore
  3. 2026-08-05 19:16 UTCEPSS rescore
  4. 2026-08-04 15:08 UTCEPSS rescore
  5. 2026-08-04 10:36 UTCEPSS rescore
  6. 2026-08-03 10:34 UTCEPSS rescore
  7. 2026-08-02 02:25 UTCEPSS rescore
  8. 2026-08-02 02:25 UTCEPSS rescore
  9. 2026-08-01 04:14 UTCEPSS rescore
  10. 2026-07-30 16:26 UTCEPSS rescore
  11. 2026-07-30 16:26 UTCEPSS rescore
  12. 2026-07-30 01:29 UTCEPSS rescore
  13. 2026-07-28 15:34 UTCEPSS rescore
  14. 2026-07-27 14:11 UTCEPSS rescore
  15. 2026-07-26 14:53 UTCEPSS rescore
  16. 2026-07-26 14:53 UTCEPSS rescore
  17. 2026-07-25 14:16 UTCEPSS rescore
  18. 2026-07-24 14:16 UTCEPSS rescore
  19. 2026-07-23 14:17 UTCEPSS rescore
  20. 2026-07-23 02:35 UTCEG score recompute
  21. 2026-07-22 14:07 UTCEPSS rescore
  22. 2026-07-21 15:23 UTCEPSS rescore
  23. 2026-07-20 17:06 UTCEPSS rescore
  24. 2026-07-19 14:30 UTCEPSS rescore
  25. 2026-07-19 14:30 UTCEPSS rescore
Show 75 more
  1. 2026-07-19 02:28 UTCEPSS rescore
  2. 2026-07-19 02:28 UTCEPSS rescore
  3. 2026-07-18 10:03 UTCEPSS rescore
  4. 2026-07-18 10:03 UTCEPSS rescore
  5. 2026-07-16 17:01 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-15 16:56 UTCEPSS rescore
  8. 2026-07-15 01:59 UTCEPSS rescore
  9. 2026-07-15 01:59 UTCEPSS rescore
  10. 2026-07-13 22:28 UTCEPSS rescore
  11. 2026-07-13 06:11 UTCEPSS rescore
  12. 2026-07-12 05:45 UTCEPSS rescore
  13. 2026-07-11 08:26 UTCEPSS rescore
  14. 2026-07-11 08:26 UTCEPSS rescore
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-08 15:13 UTCEPSS rescore
  17. 2026-07-07 13:45 UTCEPSS rescore
  18. 2026-07-07 13:45 UTCEPSS rescore
  19. 2026-07-06 16:26 UTCEPSS rescore
  20. 2026-07-06 16:26 UTCEPSS rescore
  21. 2026-07-06 02:22 UTCEPSS rescore
  22. 2026-07-06 02:22 UTCEPSS rescore
  23. 2026-07-05 02:29 UTCEPSS rescore
  24. 2026-07-04 06:30 UTCEPSS rescore
  25. 2026-07-02 17:00 UTCEPSS rescore
  26. 2026-07-01 15:05 UTCEPSS rescore
  27. 2026-06-30 23:21 UTCEPSS rescore
  28. 2026-06-30 23:21 UTCEPSS rescore
  29. 2026-06-29 14:05 UTCEPSS rescore
  30. 2026-06-28 14:06 UTCEPSS rescore
  31. 2026-06-28 14:06 UTCEPSS rescore
  32. 2026-06-28 04:55 UTCEPSS rescore
  33. 2026-06-28 04:55 UTCEPSS rescore
  34. 2026-06-27 03:07 UTCEPSS rescore
  35. 2026-06-27 03:07 UTCEPSS rescore
  36. 2026-06-25 13:49 UTCEPSS rescore
  37. 2026-06-25 13:48 UTCEPSS rescore
  38. 2026-06-24 14:04 UTCEPSS rescore
  39. 2026-06-24 14:04 UTCEPSS rescore
  40. 2026-06-23 21:32 UTCEPSS rescore
  41. 2026-06-23 21:32 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-22 14:24 UTCEPSS rescore
  44. 2026-06-21 14:55 UTCEPSS rescore
  45. 2026-06-21 14:55 UTCEPSS rescore
  46. 2026-06-21 01:58 UTCEPSS rescore
  47. 2026-06-21 01:58 UTCEPSS rescore
  48. 2026-06-19 19:25 UTCEPSS rescore
  49. 2026-06-19 19:24 UTCEPSS rescore
  50. 2026-06-18 17:51 UTCEPSS rescore
  51. 2026-06-18 17:51 UTCEPSS rescore
  52. 2026-06-17 17:52 UTCEPSS rescore
  53. 2026-06-17 17:52 UTCEPSS rescore
  54. 2026-06-16 17:52 UTCEPSS rescore
  55. 2026-06-16 17:51 UTCEPSS rescore
  56. 2026-06-15 17:47 UTCEPSS rescore
  57. 2026-06-14 23:16 UTCEPSS rescore
  58. 2026-06-13 22:59 UTCEPSS rescore
  59. 2026-06-13 22:59 UTCEPSS rescore
  60. 2026-06-12 23:11 UTCEPSS rescore
  61. 2026-06-12 23:11 UTCEPSS rescore
  62. 2026-06-11 13:59 UTCEPSS rescore
  63. 2026-06-10 22:17 UTCEPSS rescore
  64. 2026-06-10 13:21 UTCEPSS rescore
  65. 2026-06-10 13:21 UTCEPSS rescore
  66. 2026-06-08 14:16 UTCEPSS rescore
  67. 2026-06-07 15:24 UTCEPSS rescore
  68. 2026-06-07 15:24 UTCEPSS rescore
  69. 2026-06-06 13:46 UTCEPSS rescore
  70. 2026-06-06 13:46 UTCEPSS rescore
  71. 2026-06-05 22:46 UTCEPSS rescore
  72. 2026-06-05 22:46 UTCEPSS rescore
  73. 2026-06-05 06:09 UTCEPSS rescore
  74. 2026-06-05 06:09 UTCEPSS rescore
  75. 2026-06-04 13:11 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-29210?
CVE-2024-29210 is a low vulnerability published on May 7, 2024. A local privilege escalation (LPE) vulnerability has been identified in Phish Alert Button for Outlook (PAB), specifically within its configuration management functionalities. This vulnerability allows a regular user to modify the application's configuration file to redirect update checks to an…
When was CVE-2024-29210 disclosed?
CVE-2024-29210 was first published in the National Vulnerability Database on May 7, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-29210 actively exploited?
CVE-2024-29210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.5% of all scored CVEs.
What is the CVSS score of CVE-2024-29210?
CVE-2024-29210 has a CVSS v3 base score of 2.8 (NVD).
How do I remediate CVE-2024-29210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-29210, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-29210

Explore →

Is Your Infrastructure Affected by CVE-2024-29210?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.