PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-85126 Crowdfundly CVE debrief

The Crowdfundly WordPress plugin through 2.2.2 does not have capability checks on some of its AJAX actions, allowing users holding one of its own low privileged roles to grant themselves the administrator role or arbitrary capabilities, leading to a full site takeover. This vulnerability allows low-privileged users to potentially escalate privileges and take over a WordPress site. Defenders should assess exposure and prioritize verification and potential updates to prevent site takeovers.

Vendor
Crowdfundly
Product
Crowdfundly WordPress plugin
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-11
Original CVE updated
2026-10-11
Advisory published
2026-10-11
Advisory updated
2026-10-11

Who should care

WordPress administrators and security teams should assess exposure and prioritize verification and potential updates to prevent site takeovers. They should verify the presence of Crowdfundly WordPress plugin version 2.2.2 or earlier in their WordPress installation and assess exposure by checking if low-privileged roles are used.

Why it matters

Defenders should care about CVE-2026-85126 because it allows low-privileged users to potentially escalate privileges and take over a WordPress site.

  • Potential privilege escalation for low-privileged users.
  • Possible full site takeover by exploiting the vulnerability.

Technical summary

The Crowdfundly WordPress plugin through 2.2.2 is vulnerable to privilege escalation due to lacking capability checks on some AJAX actions. This allows low-privileged users to potentially escalate privileges and take over a WordPress site. The vulnerability is caused by inadequate checks on AJAX actions, which can be exploited by low-privileged users to gain elevated privileges. Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess exposure, especially if low-privileged roles are used.

Defensive priority

Defenders should prioritize verifying the presence of this vulnerability in their WordPress installations and assess exposure, especially if low-privileged roles are used.

Recommended defensive actions

  • Verify the presence of Crowdfundly WordPress plugin version 2.2.2 or earlier in your WordPress installation.
  • Assess exposure by checking if low-privileged roles are used.
  • Consider updating the plugin to a version that includes capability checks for AJAX actions.
  • Review compensating controls for exposed systems while remediation is scheduled and verified.
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review.
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented.
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability, with the primary source being a WordPress plugin vulnerability report. The Crowdfundly WordPress plugin through 2.2.2 has a known vulnerability that allows low-privileged users to escalate privileges. Defenders should verify the presence of this vulnerability in their WordPress installations and assess exposure, especially if low-privileged roles are used.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-85126 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-85126

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-85126 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-85126

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.