How to Fix CVE-2026-4117: CWE-862 Missing Authorization in CalJ Shabbat Times
By Sai Kiran Pandrala
Related fixes
Other vulnerabilities in the same area that are worth patching alongside this one:
- How to Fix CVE-2026-25328: Path Traversal in Product File Upload for WooCommerce — Path Traversal in Product File Upload for WooCommerce
- How to Fix CVE-2026-2450: .net misconfiguration: use of impersonation flaw in upKeeper Instant Privilege Access — .net misconfiguration: use of impersonation flaw in upKeeper Instant Privilege Access
- How to Fix CVE-2026-22428: Improper control of filename for include/require statement in php program ('php. , Improper control of filename for include/require statement in php program ('php.
- How to Fix CVE-2026-0556: Critical Vulnerability in XO Event Calendar , Critical Vulnerability in XO Event Calendar
- How to Fix CVE-2026-42266: Critical Vulnerability in jupyterlab , Critical Vulnerability in jupyterlab
Last verified: 2026-05-25
CVE-2026-4117 is a cwe-862 missing authorization in calj CalJ Shabbat Times. Fix it by upgrading to the patched build from the vendor advisory.
| Severity | CVSS 5.3 - Medium |
|---|---|
| Actively exploited? | Not currently in the CISA KEV catalog |
| Affected | CalJ Shabbat Times 0 up to (including) 1.5 |
| Fixed in | See vendor advisory |
| Type (CWE) | CWE-862: CWE-862 Missing Authorization |
What is CVE-2026-4117?
CVE-2026-4117 is a cwe-862 missing authorization flaw in calj CalJ Shabbat Times. It carries a CVSS base score of 5.3 (medium). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
From the source record: The CalJ plugin for WordPress is vulnerable to Missing Authorization in all versions up to, and including, 1.5. This is due to a missing capability check in the CalJSettingsPage class constructor, which processes the 'save-obtained-key' operation directly from POST data without verifying that the requesting user has the 'manage_options' capability, and without any nonce verification. The plugin bootstrap file (calj.php) instantiates CalJSettingsPage whenever is_admin() returns true, which is the case for any authenticated user making requests to wp-admin URLs (including admin-ajax.php). This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify the plugin's API key setting and clear the Shabbat cache, effectively taking control of the plugin's API integration.
Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.
Am I affected?
You are affected if your installation of CalJ Shabbat Times matches a version listed in the Affected row above.
Check the running version against the Affected row above using the product's admin console or --version flag.
How to fix CVE-2026-4117
Apply the vendor patch. Target the build named in the Fixed in row above (See vendor advisory). The runnable command set below covers the most common deployment patterns for CalJ Shabbat Times.
Generic upgrade pattern
If the affected product is a Linux package, upgrade via the system package manager:
# Debian / Ubuntu
sudo apt-get update && sudo apt-get upgrade -y
# RHEL / Rocky / Alma
sudo dnf upgrade --security -y
If it ships as a Windows installer, download the patched build from the vendor advisory and:
# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/d1c7df8e-2f82-4474-88ef-8c8ddaeb4656?source=cve
Start-Process msiexec.exe -ArgumentList '/i <patched-installer>.msi /qn /norestart' -Wait
Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | \
Where-Object DisplayName -match '<product-name>' | Select-Object DisplayName, DisplayVersion
After applying the patch
- Restart the service or device so the patched binary loads.
- Confirm the running version matches the Fixed in row using the verification command below.
- Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.
If you can't patch immediately
Until the patch lands, narrow the attack surface with these runnable controls.
Restrict network exposure
Block public access to the affected service at the perimeter. Allow only trusted source IPs.
# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4
# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
-RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny" -Direction Inbound -Action Block `
-Protocol TCP -LocalPort 443
Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.
How to verify the fix worked
Confirm the patched build is the one actually running.
Check the running version against the Affected row above using the product's admin console or --version flag.
Expected: a version at or above the patched build named in the vendor advisory.
Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.
Frequently asked questions
Is CVE-2026-4117 being exploited in the wild?
As of 2026-05-25, CVE-2026-4117 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.
What is the CVSS score for CVE-2026-4117?
The CVSS base score is 5.3 (Medium).
What version fixes this?
The vendor advisory names the patched build. See the References section.
Will a WAF or IDS rule alone close this?
No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.
References
- Official vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/d1c7df8e-2f82-4474-88ef-8c8ddaeb4656?source=cve
- NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-4117
- CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- Additional reference: https://plugins.trac.wordpress.org/browser/calj/trunk/CalJSettingsPage.php#L30
- Additional reference: https://plugins.trac.wordpress.org/browser/calj/tags/1.5/CalJSettingsPage.php#L30
- Additional reference: https://plugins.trac.wordpress.org/browser/calj/trunk/CalJSettingsPage.php#L25
- Additional reference: https://plugins.trac.wordpress.org/browser/calj/tags/1.5/CalJSettingsPage.php#L25
*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*