Skip to content
Fencer Intel
no cvss —

CVE-2026-121151 json

UpdraftPlus (Free & Pro) - Subscriber+ PHP Object Injection via Database Restore Whitespace Trimming

published 22h ago modified 22h ago also EUVD-2026-131997

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 38%
public exploits
0
none known

Summary

The UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 do not preserve long database values byte-for-byte when restoring a database backup, allowing users with a role as low as Subscriber to plant a serialized value that becomes a PHP Object Injection once an administrator backs up and restores the database.

No gadget chain is known in the UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 2.26.16.26, UpdraftPlus: WP Backup & Migration Plugin WordPress plugin before 1.26.16 or WordPress core, so the demonstrated effect is instantiation of an attacker-chosen class in the attacker's own requests. Exploitation requires the planted data to line up exactly with how the backup is read back, which depends on details of the attacker's row and the database dump format.

Patch / fix

  • Unknown UpdraftPlus: WP Backup & Migration Plugin 1.26.16, 2.26.16.26

Is CVE-2026-121151 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

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-21).

Exploits and checks

  • wpscan.com https://wpscan.com/vulnerability/5bba78bb-530c-4cdd-8612-d4c6f6560f86/ referenced PoC, tagged "exploit" by a source, unverified

Affected products

  • Unknown UpdraftPlus: WP Backup & Migration Plugin

Classification

Weakness
  • CWE-502 Deserialization of Untrusted Data
Technology feeds

References

Sources

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.