CVE-2025-26978
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') 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 confidenceSQL injection vulnerability in FS Poster plugin versions through 6.5.8 allows attackers to inject malicious SQL commands via improper neutralization of special elements in SQL queries.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check FS Poster plugin versionAccess your WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate FS Poster, and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/fs-poster/) for the 'Version' header in the plugin comments.Affected if The installed version is 6.5.8 or any version prior to it (e.g., 6.5.7, 6.5.6, etc.)
-
Verify the plugin is activeIn the WordPress admin under Plugins > Installed Plugins, confirm that FS Poster shows as 'Active' rather than 'Inactive' or 'Must Use'.Affected if The plugin is active and the version is 6.5.8 or lower
-
Identify SQL query usage pointsReview the FS Poster plugin files (particularly in includes/ or classes/ directories) for direct SQL query execution functions such as $wpdb->query(), $wpdb->prepare() with unparameterized input, or raw SELECT/INSERT/UPDATE/DELETE statements that incorporate user-supplied data without proper escaping.Affected if Unparameterized SQL queries exist that accept user input without sanitization
You are affected if FS Poster plugin version 6.5.8 or lower is installed and active in your WordPress environment.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate FS Poster to the latest patched version. If no update available, implement parameterized queries (prepared statements) for all database operations and apply input validation/sanitization.
FS Poster version 6.5.9 or later (check official repository for latest stable release)
- Check the WordPress admin panel or the FS Poster plugin repository for the latest available version
- If version 6.5.9 or higher is available, update the FS Poster plugin to that version
- After updating, verify the plugin functions correctly and test that the SQL injection vulnerability is resolved
- If no newer version is available from the official repository, contact the vendor (fs-code) directly or check patchstack.com for additional remediation guidance
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26978 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-26978 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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