dbcve.org
Platform ThemeWordPress extension · Pagelines

CVE-2015-10143

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-25
Fix available
A fix is available. Upgrade to 1.4.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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 Platform theme for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the *_ajax_save_options() function in all versions up to 1.4.4 (exclusive). This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 Platform theme for WordPress is vulnerable to an Insecure Direct Object Reference (IDOR) or missing capability check on AJAX functions (*_ajax_save_options), allowing unauthenticated attackers to update arbitrary WordPress options. This can be exploited to change the default user registration role to administrator and enable user registration, enabling attackers to create admin accounts and fully compromise the site.

MitigationUpdate the Platform theme to version 1.4.4 or later which includes proper capability checks. If updating is not possible, remove the theme entirely or implement interim firewall rules to block the vulnerable AJAX endpoints.

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
Platform ThemeWordPress extension
Affected:< 1.4.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 Platform theme is installed
    Log in to WordPress admin, go to Appearance > Themes, and check if the 'Platform' theme by Pagelines is installed or active.
    Affected if The Platform theme appears in the themes directory or is currently activated.
  2. Identify installed Platform theme version
    If the theme is installed, locate the style.css file within the theme directory (typically wp-content/themes/platform/style.css) and check the 'Version' header in the file comments.
    Affected if The version number found is less than 1.4.4.
  3. Verify AJAX endpoints are accessible
    Test accessing the theme AJAX handlers directly by making a POST request to wp-admin/admin-ajax.php with the action parameter matching the *_ajax_save_options pattern (such as platform_ajax_save_options). Since no authentication is required for the vulnerability, the endpoint will respond if vulnerable.
    Affected if The AJAX endpoint responds without requiring authentication, indicating the missing capability check is present.
  4. Check for unauthorized administrator accounts
    In WordPress admin, go to Users > All Users and review the list for any administrator accounts that you did not create or that are unfamiliar.
    Affected if Unexpected administrator accounts exist, suggesting the vulnerability may have been exploited.
  5. Review WordPress registration and role settings
    In WordPress admin, go to Settings > General and check 'New User Default Role' and verify that 'Anyone can register' is not enabled unless intentionally configured.
    Affected if The default user role has been changed to Administrator or user registration has been enabled unexpectedly.

Your site is affected if the Platform theme version is below 1.4.4 and the vulnerable AJAX endpoints are accessible without authentication.

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
Upgrade available Upgrade to 1.4.4 or later
Fixed in 1.4.4
Interim mitigation

Update the Platform theme to version 1.4.4 or later which includes proper capability checks. If updating is not possible, remove the theme entirely or implement interim firewall rules to block the vulnerable AJAX endpoints.

Recommended fix High confidence

Platform Theme 1.4.4 or later

  1. Upgrade the Platform Theme for WordPress to version 1.4.4 or later to resolve the missing authorization vulnerability

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

Fix this in Platform Theme Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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