CVE-2025-13358: CWE-862 Missing Authorization in codeconfig CodeConfig Accessibility
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.
AI Analysis
Technical Summary
CVE-2025-13358 identifies a missing authorization vulnerability (CWE-862) in the CodeConfig Accessibility plugin for WordPress, specifically in versions up to and including 1.0.0. The vulnerability stems from the plugin's failure to perform capability checks within the Settings::createPage() function. This function is invoked via the AJAX action ccpcaCreatePage, which can be triggered by any authenticated user with Subscriber-level access or higher. Because the plugin does not verify whether the user has appropriate permissions to create pages, attackers can exploit this flaw to create arbitrary pages that are immediately published on the WordPress site. The vulnerability affects all versions of the plugin up to 1.0.0, with no patch currently available. The CVSS 3.1 base score is 5.3 (medium severity), reflecting that the attack vector is network-based (remote), requires no privileges beyond authentication, no user interaction, and impacts integrity but not confidentiality or availability. The lack of authorization checks means that even low-privileged users can manipulate site content, which could be leveraged for malicious purposes such as injecting phishing pages, defacement, or SEO spam. Although no known exploits have been reported in the wild, the vulnerability presents a significant risk to WordPress sites using this plugin, especially those with multiple users or open registration. The issue is classified under CWE-862, emphasizing missing authorization as the root cause.
Potential Impact
For European organizations, the primary impact of this vulnerability is the potential for unauthorized content injection on WordPress sites using the CodeConfig Accessibility plugin. This can undermine the integrity of corporate websites, leading to reputational damage, loss of customer trust, and potential legal liabilities if malicious content such as phishing pages or misinformation is published. While confidentiality and availability are not directly affected, the ability to publish arbitrary pages can facilitate social engineering attacks or SEO poisoning campaigns targeting European users. Organizations with public-facing WordPress sites, especially those in sectors like e-commerce, finance, healthcare, and government, are at higher risk due to the potential for exploitation to harm customers or citizens. The vulnerability could also be exploited to bypass content moderation controls, complicating compliance with EU regulations such as the Digital Services Act. Given that exploitation requires only authenticated Subscriber-level access, attackers could leverage compromised or fraudulent user accounts to exploit this flaw, increasing the threat surface. The absence of known exploits in the wild suggests limited current impact but also highlights the importance of proactive mitigation to prevent future attacks.
Mitigation Recommendations
European organizations should implement the following specific mitigation measures: 1) Immediately audit WordPress installations to identify the presence of the CodeConfig Accessibility plugin and verify its version. 2) Restrict user registration and limit Subscriber-level accounts to trusted users only, reducing the risk of attacker access. 3) Temporarily disable or uninstall the plugin until an official patch or update is released by the vendor. 4) Monitor WordPress site logs and audit trails for unusual page creation activities, especially via AJAX calls to ccpcaCreatePage. 5) Implement Web Application Firewall (WAF) rules to detect and block unauthorized AJAX requests targeting the vulnerable function. 6) Educate site administrators and content managers about the risk and signs of exploitation. 7) Once a patch is available, promptly apply it and verify that capability checks are enforced in the createPage function. 8) Consider deploying additional WordPress security plugins that enforce strict role-based access controls and monitor content changes. 9) Regularly review user roles and permissions to ensure minimal privilege principles are enforced. 10) For organizations with multiple WordPress sites, centralize vulnerability management and incident response to quickly address emerging threats related to this vulnerability.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Poland, Sweden
CVE-2025-13358: CWE-862 Missing Authorization in codeconfig CodeConfig Accessibility
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.
AI-Powered Analysis
Technical Analysis
CVE-2025-13358 identifies a missing authorization vulnerability (CWE-862) in the CodeConfig Accessibility plugin for WordPress, specifically in versions up to and including 1.0.0. The vulnerability stems from the plugin's failure to perform capability checks within the Settings::createPage() function. This function is invoked via the AJAX action ccpcaCreatePage, which can be triggered by any authenticated user with Subscriber-level access or higher. Because the plugin does not verify whether the user has appropriate permissions to create pages, attackers can exploit this flaw to create arbitrary pages that are immediately published on the WordPress site. The vulnerability affects all versions of the plugin up to 1.0.0, with no patch currently available. The CVSS 3.1 base score is 5.3 (medium severity), reflecting that the attack vector is network-based (remote), requires no privileges beyond authentication, no user interaction, and impacts integrity but not confidentiality or availability. The lack of authorization checks means that even low-privileged users can manipulate site content, which could be leveraged for malicious purposes such as injecting phishing pages, defacement, or SEO spam. Although no known exploits have been reported in the wild, the vulnerability presents a significant risk to WordPress sites using this plugin, especially those with multiple users or open registration. The issue is classified under CWE-862, emphasizing missing authorization as the root cause.
Potential Impact
For European organizations, the primary impact of this vulnerability is the potential for unauthorized content injection on WordPress sites using the CodeConfig Accessibility plugin. This can undermine the integrity of corporate websites, leading to reputational damage, loss of customer trust, and potential legal liabilities if malicious content such as phishing pages or misinformation is published. While confidentiality and availability are not directly affected, the ability to publish arbitrary pages can facilitate social engineering attacks or SEO poisoning campaigns targeting European users. Organizations with public-facing WordPress sites, especially those in sectors like e-commerce, finance, healthcare, and government, are at higher risk due to the potential for exploitation to harm customers or citizens. The vulnerability could also be exploited to bypass content moderation controls, complicating compliance with EU regulations such as the Digital Services Act. Given that exploitation requires only authenticated Subscriber-level access, attackers could leverage compromised or fraudulent user accounts to exploit this flaw, increasing the threat surface. The absence of known exploits in the wild suggests limited current impact but also highlights the importance of proactive mitigation to prevent future attacks.
Mitigation Recommendations
European organizations should implement the following specific mitigation measures: 1) Immediately audit WordPress installations to identify the presence of the CodeConfig Accessibility plugin and verify its version. 2) Restrict user registration and limit Subscriber-level accounts to trusted users only, reducing the risk of attacker access. 3) Temporarily disable or uninstall the plugin until an official patch or update is released by the vendor. 4) Monitor WordPress site logs and audit trails for unusual page creation activities, especially via AJAX calls to ccpcaCreatePage. 5) Implement Web Application Firewall (WAF) rules to detect and block unauthorized AJAX requests targeting the vulnerable function. 6) Educate site administrators and content managers about the risk and signs of exploitation. 7) Once a patch is available, promptly apply it and verify that capability checks are enforced in the createPage function. 8) Consider deploying additional WordPress security plugins that enforce strict role-based access controls and monitor content changes. 9) Regularly review user roles and permissions to ensure minimal privilege principles are enforced. 10) For organizations with multiple WordPress sites, centralize vulnerability management and incident response to quickly address emerging threats related to this vulnerability.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-11-18T15:51:31.791Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6933c71e11163305efef3dc8
Added to database: 12/6/2025, 6:03:10 AM
Last enriched: 12/13/2025, 7:07:05 AM
Last updated: 2/7/2026, 11:16:48 AM
Views: 51
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2083: SQL Injection in code-projects Social Networking Site
MediumCVE-2026-2082: OS Command Injection in D-Link DIR-823X
MediumCVE-2026-2080: Command Injection in UTT HiPER 810
HighCVE-2026-2079: Improper Authorization in yeqifu warehouse
MediumCVE-2026-1675: CWE-1188 Initialization of a Resource with an Insecure Default in brstefanovic Advanced Country Blocker
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.