dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-12563

HIGH · 8.8 CVSS v3.1 Published 2025-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 s2Member Pro plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 250214 via the 'template' attribute. This makes it possible for authenticated attackers, with contributor-level and above permissions, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve 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 s2Member Pro WordPress plugin is vulnerable to Local File Inclusion (LFI) via the 'template' attribute in all versions up to 250214. Authenticated attackers with contributor-level or higher permissions can manipulate the template parameter to include and execute arbitrary files on the server, allowing execution of any PHP code present in those files.

MitigationUpdate s2Member Pro to a version beyond 250214 once available. In the interim, restrict contributor-level permissions, implement WAF rules to block directory traversal patterns in the template parameter, and review user role capabilities.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 s2Member Pro is installed
    Check the WordPress plugin directory for s2Member Pro files, or view the installed plugins via WordPress admin under Plugins > Installed Plugins
    Affected if s2Member Pro plugin is active on the WordPress site
  2. Identify the installed s2Member Pro version
    In WordPress admin, go to Plugins > Installed Plugins and locate the version number listed for s2Member Pro, or check the version defined in the main plugin file (typically s2member/includes/classes/custom-files.php or similar main plugin file)
    Affected if The installed version is 250214 or earlier
  3. Verify contributor-level user accounts exist
    In WordPress admin, go to Users and review the role assigned to each user; contributor role and higher (author, editor, administrator) grant the permissions needed to exploit this flaw
    Affected if Any user account has contributor, author, editor, or administrator role and the s2Member Pro version is vulnerable
  4. Check if s2Member Pro template functionality is accessible
    Review the s2Member Pro settings to confirm the template attribute feature is enabled or accessible to contributor-level users; this is typically found in s2Member > General Options > Login Welcome Pages or similar template routing settings
    Affected if The template routing feature is accessible to users with contributor-level permissions

A site is affected if s2Member Pro is installed with version 250214 or earlier and any authenticated user with contributor-level or higher access exists 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 s2Member Pro to a version beyond 250214 once available. In the interim, restrict contributor-level permissions, implement WAF rules to block directory traversal patterns in the template parameter, and review user role capabilities.

Recommended fix Moderate confidence

s2Member Pro version 250215 or later (any version higher than 250214)

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate s2Member Pro in the plugin list
  4. Check the current version number installed
  5. Navigate to Plugins > Add New > Upload (or check for updates)
  6. If an update is available, click 'Update Now'
  7. After updating, verify the new version is at least 250215 or later
  8. Confirm the vulnerability is resolved by ensuring the 'template' attribute no longer accepts arbitrary file paths
Caveat Review plugin settings after upgrade as minor configuration changes may occur with major version updates

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
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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