dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-11734

MEDIUM · 5.4 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The Broken Link Checker by AIOSEO – Easily Fix/Monitor Internal and External links plugin for WordPress is vulnerable to unauthorized post modification due to missing authorization in all versions up to, and including, 1.2.5. This is due to the plugin registering a REST API endpoint that only checks for a broad capability (aioseo_blc_broken_links_page) that is granted to contributor level users, without verifying the user's permission to perform actions on the specific post being targeted. This makes it possible for authenticated attackers, with contributor level access and above, to trash arbitrary posts via the DELETE /wp-json/aioseoBrokenLinkChecker/v1/post endpoint.

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 confidence

The Broken Link Checker by AIOSEO plugin registers a REST API endpoint (DELETE /wp-json/aioseoBrokenLinkChecker/v1/post) that only validates for a broad capability (aioseo_blc_broken_links_page) granted to contributor-level users, but fails to verify the user's authorization to modify the specific post being targeted. This allows authenticated attackers with contributor-level access to trash arbitrary posts on the WordPress site.

MitigationUpdate to version 1.2.6 or later which includes proper post-level authorization checks, or remove the aioseo_blc_broken_links_page capability from contributor roles if immediate updating is not feasible.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm AIOSEO Broken Link Checker plugin is installed
    Go to WordPress admin > Plugins and look for 'Broken Link Checker by AIOSEO' in the installed plugins list, or check the plugins directory /wp-content/plugins/aioseo-broken-link-checker/
    Affected if Plugin is installed and active
  2. Check installed plugin version
    In WordPress admin > Plugins, click on the plugin to view its details and note the version number, then compare against version 1.2.6
    Affected if Version is before 1.2.6
  3. Verify contributor role has the vulnerable capability
    Use a role editor plugin or query the WP database: SELECT meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%aioseo_blc_broken_links_page%'; alternatively check via WP-CLI: wp user list --role=contributor --fields=ID,user_login
    Affected if Contributor role or any contributor-level user has the aioseo_blc_broken_links_page capability assigned
  4. Test REST API endpoint accessibility
    Send an authenticated request as a contributor user to: DELETE /wp-json/aioseoBrokenLinkChecker/v1/post with a JSON body containing a target post ID, for example: curl -X DELETE https://example.com/wp-json/aioseoBrokenLinkChecker/v1/post -H 'Content-Type: application/json' -u contributor_username:contributor_password -d '{"post_id":999}'
    Affected if Endpoint accepts the request and returns a successful response without verifying ownership of the targeted post ID

User is affected if the plugin version is before 1.2.6 and the aioseo_blc_broken_links_page capability is granted to contributor-level users, allowing them to trash arbitrary posts via the unprotected REST API endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.2.6 or later which includes proper post-level authorization checks, or remove the aioseo_blc_broken_links_page capability from contributor roles if immediate updating is not feasible.

Recommended fix High confidence

1.2.6

  1. 1. Log in to the WordPress admin dashboard with administrator privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Broken Link Checker by AIOSEO' plugin
  4. 4. If an update is available, click 'Update Now' to install version 1.2.6 or later
  5. 5. Verify the update completed successfully by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11734 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11734 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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