WordPress BA Book Everything plugin <= 1.8.33 - Cross Site Scripting (XSS) vulnerability
The BA Book Everything plugin for WordPress, versions up to and including 1.8.33, is affected by this cross-site scripting flaw. Fixed in 1.8.34.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.8.34
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Unauthenticated Cross Site Scripting (XSS) in BA Book Everything <= 1.8.33 versions.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- ba-book-everything
through 1.8.33
References 1
Questions about CVE-2026-39786
What does this mean?
An attacker can inject malicious scripts into the site that steal visitor data or hijack visitor accounts.Source: patchstack.com
Am I affected, and how do I check?
Versions of the BA Book Everything plugin up to and including 1.8.33 are listed as affected, with no additional conditions given. To check a site's version, look at the installed plugin version on the WordPress Plugins screen.Source: patchstack.com
What should I do about it?
Update the BA Book Everything plugin to version 1.8.34 or later, which resolves the vulnerability.Source: patchstack.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data