CVE-2025-13358
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Accessiy By CodeConfig Accessibility plugin for WordPress fails to enforce authorization in the Settings::createPage() function, allowing any authenticated user with Subscriber-level permissions or higher to create arbitrary published pages via the ccpcaCreatePage AJAX action.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Accessiy plugin is installedGo to WordPress admin > Plugins and check if 'Accessiy By CodeConfig Accessibility' is listed as activeAffected if The plugin is installed and active on the WordPress site
-
Identify installed plugin versionIn Plugins list, click on the plugin name or view the plugin files to find the version number in the plugin header commentAffected if The installed version lacks proper capability checks on the ccpcaCreatePage AJAX action (any version without 'manage_options' verification before page creation)
-
Check AJAX action accessibilityInspect the plugin PHP code, specifically the handler for 'ccpcaCreatePage' action, and verify what capability is required (look for 'manage_options' or similar admin-level capability)Affected if The AJAX handler accepts requests from users with 'subscriber' level or does not verify capabilities at all
-
Audit created pages for unauthorized contentIn WordPress admin > Pages, review the list of published pages - check for any pages created without admin authorization, especially those with suspicious content or created at unexpected timesAffected if There are published pages that were created by lower-privileged users or without proper admin authentication
The site is affected if the Accessiy By CodeConfig Accessibility plugin is installed and the ccpcaCreatePage AJAX action permits page creation by users with Subscriber-level permissions or lower.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to a version with proper capability checks (e.g., 'manage_options') enforced before page creation, or disable the plugin until a patched version is available.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13358 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data