dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2023-4730

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 LadiApp plugn for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the init_endpoint() function hooked via 'init' in versions up to, and including, 4.3. This makes it possible for unauthenticated attackers to modify a variety of settings. An attacker can directly modify the 'ladipage_key' which enables them to create new posts on the website and inject malicious web scripts.

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 up to v4.3 lacks a capability check on the init_endpoint() function hooked via WordPress's 'init' action. This allows unauthenticated attackers to directly modify plugin settings including 'ladipage_key', enabling arbitrary post creation and malicious script injection.

MitigationUpdate to version 4.4 or later which implements proper capability checks. If no update is available, remove the plugin or restrict init endpoint access via web server configuration.

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 checks

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

  1. Verify LadiApp plugin is installed
    Navigate to WordPress admin > Plugins, or inspect the /wp-content/plugins/ directory for a folder named 'ladipage' or 'ladiapp'
    Affected if The LadiApp plugin folder exists in the plugins directory
  2. Check installed plugin version
    In WordPress admin > Plugins, find LadiApp and view the version number displayed under the plugin name, or read the main plugin PHP file header for 'Version:' tag
    Affected if The version number is 4.3 or lower (any version up to and including 4.3)
  3. Confirm the vulnerable init hook exists
    Access the site and make a request to the WordPress init endpoint (the root index.php) - the init_endpoint() function runs on every page load via add_action('init', 'init_endpoint'). Use a proxy or check server logs for any LadiApp-related API calls being processed without authentication.
    Affected if Requests to the site trigger the plugin's init endpoint without requiring admin authentication
  4. Inspect plugin settings for unauthorized modifications
    In WordPress admin > LadiApp settings (if accessible), check the 'ladipage_key' setting and any settings related to post creation or custom posts. Also check the wp_options table for option_name containing 'ladiapp' or 'ladipage'.
    Affected if The 'ladipage_key' option is present and set, or there are unexpected post type entries created by the plugin that were not created by an administrator

A user is affected if the LadiApp plugin is installed at version 4.3 or lower and the init endpoint is accessible without authentication, allowing settings modification.

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 4.4 or later which implements proper capability checks. If no update is available, remove the plugin or restrict init endpoint access via web server configuration.

Recommended fix Moderate confidence

Version 4.4 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the LadiApp plugin
  4. Check the current version number
  5. Update the plugin to the latest available version (version 4.4 or higher)

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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