dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-12252

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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 SEO LAT Auto Post plugin for WordPress is vulnerable to file overwrite due to a missing capability check on the remote_update AJAX action in all versions up to, and including, 2.2.1. This makes it possible for unauthenticated attackers to overwrite the seo-beginner-auto-post.php file which can be leveraged to achieve remote code execution.

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 SEO LAT Auto Post WordPress plugin has a missing capability check on the remote_update AJAX action, allowing unauthenticated attackers to overwrite the seo-beginner-auto-post.php file. This arbitrary file write capability enables remote code execution.

MitigationUpdate the plugin to the latest version (beyond 2.2.1) to patch the missing authorization check, or disable and remove the plugin if no update is available. Audit for any unauthorized file modifications and compromised accounts.

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
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 plugin installation
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'SEO LAT Auto Post' or check the plugin directory wp-content/plugins/ for folders containing 'seo-lat-auto-post' or similar SEO/auto-post related names
    Affected if The plugin is installed on the WordPress site
  2. Identify installed version
    In Plugins list, click on the plugin to view details, or check the plugin's main PHP file header for 'Version:' tag. Common path: wp-content/plugins/[plugin-folder]/seo-beginner-auto-post.php or similar
    Affected if Version is 2.2.1 or lower (versions up to 2.2.1 lack the capability check fix)
  3. Verify AJAX action exposure
    Inspect the main plugin PHP file for 'add_action("wp_ajax_remote_update"' or 'add_action("wp_ajax_nopriv_remote_update"' calls. Also check admin-ajax.php?action=remote_update returns a response (even an error indicates the action exists)
    Affected if The remote_update AJAX action is registered and accessible without authentication (wp_ajax_nopriv_ hook present)
  4. Confirm file overwrite capability exists
    Search the plugin source code for file write operations (file_put_contents, fwrite, etc.) targeting seo-beginner-auto-post.php or dynamic file paths controlled by AJAX parameters
    Affected if The plugin contains code that writes to PHP files based on unauthenticated AJAX requests

A user is affected if the SEO LAT Auto Post plugin is installed with version 2.2.1 or lower AND the remote_update AJAX action is accessible without authentication AND the plugin contains file write functionality that can overwrite PHP files.

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 the plugin to the latest version (beyond 2.2.1) to patch the missing authorization check, or disable and remove the plugin if no update is available. Audit for any unauthorized file modifications and compromised accounts.

Recommended fix Moderate confidence

Version higher than 2.2.1 (check WordPress plugin repository for latest fixed release)

  1. Locate the SEO LAT Auto Post plugin in your WordPress installation
  2. Check the current installed version of the plugin
  3. Navigate to Plugins > Add New > Upload Plugin or update through the WordPress plugin repository
  4. Update to the latest available version of the SEO LAT Auto Post plugin (version higher than 2.2.1)
  5. Verify the update was successful and the plugin is functioning correctly
  6. If no update is available from the WordPress repository, consider using an alternative SEO auto-posting plugin or contact the plugin developer directly

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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