CVE-2025-14867
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 · uneditedThe Flashcard plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 0.9 via the 'source' attribute of the 'flashcard' shortcode. This makes it possible for authenticated attackers, with contributor level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
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 confidenceThe Flashcard WordPress plugin versions up to 0.9 contains a path traversal vulnerability in the 'flashcard' shortcode handling. The 'source' attribute fails to properly sanitize input, allowing authenticated users with contributor-level permissions or higher to use directory traversal sequences (e.g., ../../) to read arbitrary files on the server filesystem.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Flashcard plugin versionAccess WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate the Flashcard plugin, and note the version number displayed. Compare this version against the affected range (versions up to and including 0.9).Affected if The installed version is 0.9 or lower.
-
Verify flashcard shortcode is activeCheck if the flashcard shortcode is available by attempting to use [flashcard] in a post or page, or by examining the plugin source code to confirm shortcode registration via add_shortcode('flashcard', ...).Affected if The shortcode is registered and functional in the WordPress installation.
-
Identify users with contributor-level or higher accessIn WordPress admin, go to Users > All Users and review the role assigned to each user. Contributor, Author, Editor, and Administrator roles all have permissions equal to or greater than contributor-level.Affected if Any user account has a role of Contributor, Author, Editor, or Administrator.
-
Examine shortcode handler for source attribute validationLocate the plugin PHP file containing the flashcard shortcode handler (typically in the plugin root directory). Inspect the code that processes the 'source' attribute to determine if directory traversal sequences are sanitized or restricted.Affected if The source attribute processing lacks proper sanitization to prevent ../ sequences from traversing directories.
The environment is affected if the Flashcard plugin version 0.9 or lower is installed, the shortcode is active, and at least one user with contributor-level or higher permissions exists, allowing potential exploitation of the path traversal vulnerability in the source attribute.
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.
From vendor dataUpdate the Flashcard plugin to the latest patched version when available. Until a patch is released, restrict or disable contributor-level access and consider removing the flashcard shortcode functionality.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-14867 — 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-14867 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