WordPress security changelog
MEDIUM CVE-2025-13358 Deferred

Accessiy By CodeConfig Accessibility: A security weakness

Accessiy By CodeConfig Accessibility is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 5.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
Accessiy By CodeConfig Accessibility
Plugin slug
codeconfig-accessibility
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Dec 06, 2025
Weakness
CWE-862 — Missing Authorization

This CVE was published Dec 06, 2025 and is one of 2 known issues for this plugin.

What to do

Update, patch or deactivate.

Update Accessiy By CodeConfig Accessibility to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The Accessiy By CodeConfig Accessibility plugin for WordPress is vulnerable to unauthorized page creation due to missing authorization checks in versions up to, and including, 1.0.0. This is due to the plugin not performing capability checks in the `Settings::createPage()` function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary published pages on the site via the `ccpcaCreatePage` AJAX action.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

References

Primary and upstream sources