dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-11454

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Specific Content For Mobile – Customize the mobile version without redirections plugin for WordPress is vulnerable to SQL Injection via the eos_scfm_duplicate_post_as_draft() function in all versions up to, and including, 0.5.5 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with COntributor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Specific Content For Mobile WordPress plugin versions up to 0.5.5 contains a SQL Injection vulnerability in the eos_scfm_duplicate_post_as_draft() function. Due to insufficient escaping of user-supplied parameters and lack of prepared statements in the existing SQL query, authenticated users with Contributor-level permissions or higher can inject arbitrary SQL queries to extract sensitive data from the database.

MitigationUpdate the plugin to the latest version when available, or implement proper input sanitization and replace dynamic SQL queries with prepared statements to prevent SQL injection.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 the plugin is installed
    Check your WordPress site's plugin directory for 'Specific Content For Mobile' or 'specific-content-for-mobile' folder, or list installed plugins via wp-cli: wp plugin list --search='*specific*content*mobile*'
    Affected if The plugin folder exists in wp-content/plugins/
  2. Identify the installed version
    Check the plugin's main PHP file (usually index.php or the primary plugin file) for the 'Version' header comment, or run: wp plugin get specific-content-for-mobile --field=version
    Affected if The version is 0.5.5 or lower (any version up to and including 0.5.5)
  3. Locate the vulnerable function
    Search the plugin files for the function eos_scfm_duplicate_post_as_draft, typically in the main plugin PHP file or includes/duplicate.php. Inspect the function for direct SQL query construction without prepared statements.
    Affected if The function exists and contains SQL queries using $wpdb->prepare without proper escaping, or concatenates user input directly into queries
  4. Confirm contributor-level users exist
    Check WordPress user roles: wp user list --role=contributor (or higher roles like author, editor, administrator). Also verify if any registered users have contributor-level access in Users > All Users.
    Affected if At least one user account with Contributor, Author, Editor, or Administrator role exists on the site

You are affected if the Specific Content For Mobile plugin is installed with version 0.5.5 or lower AND the vulnerable eos_scfm_duplicate_post_as_draft function exists AND any Contributor-level or higher user account is present 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version when available, or implement proper input sanitization and replace dynamic SQL queries with prepared statements to prevent SQL injection.

Recommended fix Moderate confidence

Upgrade to version 0.5.6 or later

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate 'Specific Content For Mobile – Customize the mobile version without redirections'
  4. 4. If an update is available, click 'Update Now'
  5. 5. Verify the updated version is 0.5.6 or higher
  6. 6. Confirm the plugin is functioning correctly after update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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