dbcve.org
LadipageWordPress extension

CVE-2023-4728

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to after 4.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 LadiApp plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the publish_lp() function hooked via an AJAX action in versions up to, and including, 4.4. This makes it possible for authenticated attackers with subscriber-level access and above to change the LadiPage key (a key fully controlled by the attacker), enabling them to freely create new pages, including web pages that trigger stored XSS

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 LadiApp WordPress plugin lacks a capability check on the publish_lp() AJAX action, allowing any authenticated user with subscriber-level access to call this function. Attackers can modify the LadiPage key (which they control) and create new pages with malicious content, leading to stored XSS.

MitigationUpdate to plugin version 4.5 or later which includes proper capability verification. Until then, restrict or disable the affected AJAX endpoint or disable user registrations on the site.

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
LadipageWordPress extension
Affected:<= 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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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 checks

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

  1. Verify LadiApp plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Ladipage Ladipage' or 'LadiApp' in the plugin list. Note whether it is active or inactive.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    On the Plugins page in WordPress admin, click on the plugin name to view details, or inspect the plugin header in the main plugin file (typically in /wp-content/plugins/ladipage/ or similar path). Compare the version number to the affected range.
    Affected if Version is 4.4 or lower
  3. Confirm user registration is enabled
    In WordPress admin, go to Settings > General and check 'Anyone can register' is enabled. Alternatively, check the 'users_can_register' option in wp-options database table.
    Affected if User registration is enabled on the site
  4. Check for subscriber or low-privilege user accounts
    Navigate to Users > All Users in WordPress admin, or query the wp_users and wp_usermeta tables. Look for users with role 'Subscriber' or other low-privilege roles.
    Affected if Any subscriber-level or low-privilege user accounts exist on the site

A site is affected if the LadiApp plugin version is 4.4 or lower, user registration is enabled, and low-privilege user accounts (subscriber or above) can exist on the site.

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 a release after 4.4
Interim mitigation

Update to plugin version 4.5 or later which includes proper capability verification. Until then, restrict or disable the affected AJAX endpoint or disable user registrations on the site.

Recommended fix High confidence

Upgrade to LadiApp (Ladipage) version 4.5 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the LadiApp (Ladipage) plugin
  4. 4. If an update is available, click 'Update Now' to update to the latest version which includes the security fix (version 4.5 or later)
  5. 5. Alternatively, you can manually upload the fixed plugin version from the WordPress plugin repository
  6. 6. After updating, verify the plugin is working correctly and test that the authorization check is now properly enforced
Caveat Review plugin settings after upgrade as some configurations may need to be re-verified

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

Fix this in Ladipage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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