CVE-2026-110507 Page Builder by SiteOrigin < 2.38.0 - Contributor+ Sensitive Data Disclosure via Post Loop Widget Query Arguments
Low 2.7
Published
Updated
Check this codebase for CVE-2026-110507 and fix it if it is affected.
What it is: CVE-2026-110507 is a low-severity vulnerability in Unknown Page Builder by SiteOrigin, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-110507 in the wild and no public exploit code.
Affected product: Unknown Page Builder by SiteOrigin. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-110507/ (Markdown: https://insights.sbomify.com/CVE-2026-110507/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-110507?
CVE-2026-110507 is a low-severity vulnerability in Unknown Page Builder by SiteOrigin, published on 28 Oct 2026.
Official description
The Page Builder by SiteOrigin WordPress plugin before 2.38.0 does not restrict the query arguments users can add to its Post Loop widget or limit the loop to posts they are allowed to read, which could allow users with the contributor role and above to read the content of other users' draft, pending, scheduled and private posts and pages.
Weakness: CWE-200
Which versions are affected by CVE-2026-110507?
How do I fix CVE-2026-110507?
No fix has been published for CVE-2026-110507 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-110507 being exploited?
There is no known exploitation of CVE-2026-110507 in the wild and no public exploit code.
Sources
Also known as GHSA-2m52-8826-2mqp.