WordPress Beelove theme <= 1.2.6 - PHP Object Injection vulnerability

published 2026-03-25 7mo ago modified 2026-06-17 4mo ago also EUVD-2026-15515

cvss: 9.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.5%; EPSS 0.5% chance of exploitation in 30 days, percentile 45%
public exploits: 0; none known

Deserialization of Untrusted Data vulnerability in AncoraThemes Beelove beelove allows Object Injection.This issue affects Beelove: from n/a through <= 1.2.6.

Is CVE-2026-22507 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 7mo ago (2026-03-26)

Exploit prediction

0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

AncoraThemes Beelove

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Theme/beelove/vulnerability/wordpress-beelove-theme-1-2-6-php-object-injection-vulnerabili
vdb-entry

Sources

CVE List CVE-2026-22507
NVD CVE-2026-22507

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.