dbcve.org
Super Store FinderWordPress extension · Superstorefinder

CVE-2023-5054

MEDIUM · 5.3 CVSS v3.1 Published 2023-09-19
Fix available
A fix is available. Upgrade to after 6.9.2 or later.
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 Super Store Finder plugin for WordPress is vulnerable to unauthenticated arbitrary email creation and relay in versions up to, and including, 6.9.3. This is due to insufficient restrictions on the sendMail.php file that allows direct access. This makes it possible for unauthenticated attackers to send emails utilizing the vulnerable site's server, with arbitrary content. Please note that this vulnerability has already been publicly disclosed with an exploit which is why we are publishing the details without a patch available, we are attempting to initiate contact with the developer.

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 Super Store Finder WordPress plugin (versions ≤6.9.3) contains a sendMail.php endpoint that lacks proper authentication and input validation checks. This allows unauthenticated attackers to directly access the file and abuse the server's mail functionality to send arbitrary emails, effectively turning the site into an open email relay.

MitigationSince no vendor patch is available, organizations should immediately restrict direct access to sendMail.php via .htaccess rules or web server configuration (e.g., Deny directive), or remove/deactivate the plugin until a secure update is released.

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
Super Store FinderWordPress extension
Affected:<= 6.9.2

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 Super Store Finder plugin is installed
    Check the WordPress plugins directory for 'super-store-finder' or 'Superstorefinder' folder, typically in wp-content/plugins/. You can also list installed plugins via WordPress admin dashboard under Plugins > Installed Plugins.
    Affected if Plugin folder exists in the WordPress plugins directory
  2. Determine installed plugin version
    Check the plugin's main PHP file (usually super-store-finder.php or similar) for the 'Version' header in the plugin comments, or view the version in WordPress admin under Plugins > Installed Plugins > Super Store Finder.
    Affected if Version number is 6.9.2 or lower (≤6.9.2)
  3. Confirm sendMail.php exists
    Locate the sendMail.php file within the plugin directory, typically at wp-content/plugins/super-store-finder/sf-admin/sendMail.php or similar path. Use file browser or find command to search for sendMail.php in the plugin folder.
    Affected if sendMail.php file is present in the plugin directory
  4. Test endpoint accessibility (if safe to do so)
    Attempt a local check of the sendMail.php file's permissions and whether it includes any authentication checks at the top of the file. Review the PHP code for require/include statements that verify user login status or nonce tokens.
    Affected if sendMail.php lacks authentication checks (no current_user check, no wp_verify_nonce, no require statements for auth files)
  5. Check web server access to the endpoint
    Review web server logs or attempt a local curl request to the sendMail.php endpoint (e.g., https://yourdomain.com/wp-content/plugins/super-store-finder/sf-admin/sendMail.php) to determine if external unauthenticated requests are processed.
    Affected if Endpoint is accessible to unauthenticated users and processes requests without authentication

Environment is affected if Super Store Finder plugin version ≤6.9.2 is installed AND the sendMail.php file exists and is accessible without authentication.

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 6.9.2
Interim mitigation

Since no vendor patch is available, organizations should immediately restrict direct access to sendMail.php via .htaccess rules or web server configuration (e.g., Deny directive), or remove/deactivate the plugin until a secure update is released.

Recommended fix Low confidence
  1. Check the official WordPress plugin repository or vendor site (superstorefinder.net) for the latest available version of Super Store Finder.
  2. If a newer version (6.9.3 or higher) is available, review the changelog to confirm the sendMail.php authorization vulnerability has been addressed.
  3. If no patched version is available, implement an immediate mitigation: configure web server (Apache/Nginx) or firewall rules to block direct external access to /wp-content/plugins/super-store-finder/sendMail.php.
  4. Alternatively, temporarily disable the Super Store Finder plugin until a patched version is released.
  5. Monitor vendor communications for security updates.

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

Fix this in Super Store Finder Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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