CVE-2026-27350: Builderius server-side request forgery (SSRF) vulnerability
high 7.2 published 2026-10-10 · updated 2026-10-13
- Affected versions
- 1.4 to 1.4-beta
- Fixed in
- unknown
- Latest version
- 1.5-rc1
- Severity
- High · CVSS 7.2
- Active installs
- 200+
- Type
- Server-side request forgery (SSRF)
What an attacker needs
- Access: None. No account or login is needed (per the CVSS score).
CVSS vector (score by Patchstack): CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
What to do now
- Update Builderius to the latest version (1.5-rc1). The record does not name a fixed version, so also read the advisory below.
- If you cannot update right away, deactivate it until you can.
- Not sure which version you run? Check your version against every known Builderius issue.
With WP-CLI:
wp plugin get builderius --field=version. - If you ran an affected version and something looks off (new admin users, spam pages, redirects), run the free scan below.
The advisory
Server-Side Request Forgery (SSRF) vulnerability in Builderius.io Builderius allows Server Side Request Forgery. This issue affects Builderius: from 1.4 through 1.4-beta.
References
- NVD CVE-2026-27350 nvd.nist.gov
- Patchstack advisory patchstack.com
Related
Ran an affected version? Check your site for signs of a hack
The free scan reads the public side of your site and looks for spam pages, hidden redirects, injected scripts and blacklist entries. No login, no install, about a minute.
Where this data comes from
- CVE record, score and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Versions and install counts: wordpress.org/plugins/builderius (Plugins API), fetched 2026-11-04.
- The summary, “what an attacker needs” and “what to do” sections are our plain-English reading of the record and the plugin's release history; the quoted description is the record's own text. Spot an error? Email Daniel.