dbcve.org
Add Any Extension To PagesWordPress extension · Infolific

CVE-2023-50873

HIGH · 8.8 CVSS v3.1 Published 2023-12-28
Fix available
A fix is available. Upgrade to after 1.4 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Marios Alexandrou Add Any Extension to Pages.This issue affects Add Any Extension to Pages: from n/a through 1.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the WordPress plugin 'Add Any Extension to Pages' by Marios Alexandrou. The plugin lacks proper CSRF protection (nonce tokens) on state-changing actions, allowing attackers to trick authenticated administrators into unknowingly performing unintended operations such as modifying page extensions.

MitigationImplement WordPress nonces on all form submissions and AJAX actions within the plugin to verify request origin and intent, and ensure nonce validation fails gracefully on mismatched tokens.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Add Any Extension To PagesWordPress extension
Affected:<= 1.4

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 plugin installation
    Locate the plugin files in your WordPress installation. The plugin is named 'Add Any Extension To Pages' by Infolific/Marios Alexandrou. Check the plugins directory for the plugin folder.
    Affected if The plugin is present in the WordPress plugins directory.
  2. Identify installed version
    Access the WordPress admin dashboard, go to Plugins > Installed Plugins, find 'Add Any Extension To Pages', and note the version number displayed.
    Affected if The installed version is 1.4 or lower (any version <= 1.4).
  3. Verify plugin is active
    In the WordPress admin under Plugins > Installed Plugins, confirm whether the 'Add Any Extension To Pages' plugin shows as Active.
    Affected if The plugin is activated on the site.
  4. Examine admin pages for state-changing forms
    Access the plugin settings page (typically under Settings > Add Any Extension to Pages or a similar admin menu item). Identify any forms that modify data, such as those that change page extensions or plugin settings.
    Affected if The plugin has admin settings pages with forms that modify configuration.
  5. Inspect plugin source code for nonce protection
    Access the main plugin PHP file (usually named similarly to the plugin slug) and search for 'wp_nonce_field', 'wp_nonce', 'check_admin_referer', or 'check_ajax_referer' around form handling code. Look for state-changing functions that process form submissions.
    Affected if The plugin code lacks nonce verification functions (wp_nonce_field, check_admin_referer, etc.) on state-changing form handlers.

You are affected if the Add Any Extension To Pages plugin (version 1.4 or lower) is installed and active on your WordPress site, and its code does not implement WordPress nonce tokens on forms that modify settings or page extensions.

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.

From vendor data
Upgrade available Upgrade to a release after 1.4
Interim mitigation

Implement WordPress nonces on all form submissions and AJAX actions within the plugin to verify request origin and intent, and ensure nonce validation fails gracefully on mismatched tokens.

Fix this in Add Any Extension To Pages Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50873 — 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-2023-50873 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