dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-30960

HIGH · 8.3 CVSS v3.1 Published 2025-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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
Missing Authorization vulnerability in fs-code FS Poster fs-poster.This issue affects FS Poster: from n/a through <= 6.5.8.

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 · moderate confidence

This is a missing authorization vulnerability in the FS Poster WordPress plugin (versions through 6.5.8) that allows unauthorized users to access functionality they should not have permission to use. The high CVSS score (8.3) indicates the vulnerability is exploitable and can lead to significant impact, likely allowing attackers to bypass access controls and perform actions reserved for authenticated users with higher privileges.

MitigationUpdate FS Poster to the latest version as soon as a patch is released. Review user roles and capabilities within the WordPress admin and ensure least-privilege principles are applied to accounts until the patch is applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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. Check if FS Poster plugin is installed
    Navigate to WordPress admin > Plugins and look for 'FS Poster' in the installed plugins list, or inspect the directory wp-content/plugins/ for a folder named 'fs-poster' or similar
    Affected if FS Poster plugin is found in the plugins directory
  2. Identify the installed FS Poster version
    In WordPress admin > Plugins > Installed Plugins, find FS Poster and note the version number displayed under the plugin name. Alternatively, open the main plugin file (e.g., fs-poster.php) and look for the Version header in the plugin comment block
    Affected if The version number is 6.5.8 or lower (any version through 6.5.8)
  3. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, verify that FS Poster shows as 'Active' rather than 'Inactive'
    Affected if FS Poster is currently activated on the site
  4. Check for enabled user registration or public posting features
    Review the FS Poster settings in the WordPress admin panel (Settings > FS Poster or under the plugin menu) for any features that allow front-end submissions, public API access, or scheduled posting without authentication
    Affected if Any feature that allows unauthenticated or low-privileged users to trigger posting actions is enabled

If FS Poster version 6.5.8 or below is installed and active on the WordPress site, the missing authorization vulnerability is present.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update FS Poster to the latest version as soon as a patch is released. Review user roles and capabilities within the WordPress admin and ensure least-privilege principles are applied to accounts until the patch is applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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