CVE-2026-1042
CVSS 4.4 MediumEPSS 0.1%
- CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N
- Published: 2026-01-20T06:16:00.477
The WP Hello Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘digit_one’ and ‘digit_two’ parameters in all versions up to, and including, 1.02 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
Related CVE by CWE
No related CWE found.
Top CVE for Vendor
No vendor taxonomy on this entry.
Recently Exploited Similar Vulnerabilities
No recent KEV-listed items for this vendor/product.
How to fix CVE-2026-1042
CVE-2026-1042 is a medium severity vulnerability affecting the affected product.
Description: The WP Hello Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘digit_one’ and ‘digit_two’ parameters in all versions up to, and including, 1.02 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that […]
Affected Versions:
❌ Vulnerable: ≤ 1.02
✅ Safe: ≥ 1.3
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
- Check if you're running the affected product
- Verify version (vulnerable: ≤ 1.02)
- Update to ≥ 1.3 or later
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Description: The WP Hello Bar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘digit_one’ and ‘digit_two’ parameters in all versions up to, and including, 1.02 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level access and above, to inject arbitrary web scripts in pages that […]
Affected Versions:
❌ Vulnerable: ≤ 1.02
✅ Safe: ≥ 1.3
Exploit Difficulty: HARD
⏱️ Time to exploit: > 4 hours
🛠️ Required skills: Advanced security expertise
💰 Public exploits: Rare or not public
How to Fix:
1 Identify affected systems
- Check if you're running the affected product
- Verify version (vulnerable: ≤ 1.02)
2 Immediate actions
- Update to ≥ 1.3 or later
- If patching is not immediately possible: restrict network exposure, apply least-privilege access
3 Verification
- Test the fix in a staging environment first
- Review logs for signs of exploitation
- Monitor for IOCs (Indicators of Compromise)
4 Long-term prevention
- Enable automatic security updates
- Set up vulnerability monitoring
- Review and harden security configurations
Exploit Difficulty Assessment
HARD
Time to Exploit: > 4 hours
Skills Required: Advanced security expertise
Public Exploits: Rare or not public
Affected Versions
Vulnerable: ≤ 1.02
Safe: ≥ 1.3
Vulnerability Timeline
Jan 20, 2026
Vulnerability Published
CVE details first published to NVD database
Jan 20, 2026
Imported to Database
Added to this CVE tracking system
Detection Rules & IOCs
No specific detection rules generated for this vulnerability type.
No vendor/product data available.