dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-1678

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-02
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 Subway – Private Site Option plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.1.4 via the REST API. This makes it possible for unauthenticated attackers to bypass the plugin's private site feature and view restricted page and post content.

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 Subway WordPress plugin has a REST API vulnerability that allows unauthenticated attackers to bypass the plugin's private site protection and access restricted page and post content that should only be visible to logged-in users.

MitigationUpdate the Subway – Private Site Option plugin to version 2.1.5 or later to resolve the REST API authorization bypass.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Subway plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for the 'subway' or 'subway-private-site-option' folder
    Affected if The Subway plugin is present on the WordPress site
  2. Check installed Subway plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Subway - Private Site Option plugin. The version number is displayed below the plugin name. Alternatively, check the main plugin file header for the 'Version' tag
    Affected if The installed version is lower than 2.1.5 (versions prior to 2.1.5 are affected)
  3. Confirm private site protection is enabled
    In WordPress admin, go to Subway > Settings or the plugin settings page. Check if the private site mode or login wall is turned on (this is the protection that the vulnerability bypasses)
    Affected if Private site protection is enabled and the plugin version is below 2.1.5
  4. Test REST API access without authentication
    Send a GET request to the WordPress REST API endpoint (for example: /wp-json/wp/v2/posts or /wp-json/subway/v1/...) using a tool like curl or browser DevTools, without providing any authentication cookies or headers
    Affected if The REST API returns content that should only be visible to logged-in users when accessed without authentication, confirming the bypass is exploitable

The site is affected if the Subway plugin version is below 2.1.5 and private site protection is enabled, as unauthenticated users can access restricted content via the REST API.

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 Subway – Private Site Option plugin to version 2.1.5 or later to resolve the REST API authorization bypass.

Recommended fix High confidence

Latest version after 2.1.4 (check wordpress.org for current stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the Subway – Private Site Option plugin
  4. Check if an update is available and install the latest version
  5. Alternatively, download the latest version from wordpress.org and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the private site functionality still works as expected and that restricted content is no longer accessible via REST API without authentication

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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