CVE-2025-2805
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 ORDER POST plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to, and including, 2.0.2. This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.
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 ORDER POST WordPress plugin (versions up to 2.0.2) contains an arbitrary shortcode execution vulnerability due to insufficient input validation before calling do_shortcode(). An unauthenticated attacker can supply crafted input that gets processed as a shortcode, potentially triggering actions from other installed plugins or themes.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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.
-
Confirm ORDER POST plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'ORDER POST' in the list of active plugins.Affected if The plugin appears in the installed plugins list and is activated.
-
Identify the installed versionIn the WordPress admin, go to Plugins > Installed Plugins and locate ORDER POST. The version number is displayed below the plugin name.Affected if The version number is 2.0.2 or lower.
-
Locate the vulnerable input parameterExamine the plugin source code (typically in wp-content/plugins/order-post/) and search for calls to do_shortcode(). Identify which GET or POST parameter is passed to this function without validation.Affected if A user-controllable parameter is directly passed to do_shortcode() without sanitization.
-
Verify the parameter is accessible to unauthenticated usersTest accessing the plugin page or form where the vulnerable parameter is submitted without logging in. Submit a test request with a benign shortcode pattern like [test] to confirm it gets processed.Affected if The request is processed and the shortcode is executed without requiring authentication.
-
Review request logs for exploitation attemptsCheck web server access logs (Apache/Nginx) for requests to pages utilizing the ORDER POST plugin that contain shortcode-like patterns such as brackets [ ] in query parameters or form fields.Affected if Logs contain requests with shortcode syntax in parameters related to this plugin.
A user is affected if the ORDER POST plugin is installed with version 2.0.2 or lower and the vulnerable parameter accepting shortcode input is accessible without authentication.
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 ORDER POST plugin to version 2.0.3 or later which includes proper validation of input before the do_shortcode call. Until updated, monitor for suspicious requests containing shortcode-like patterns.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2805 — 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-2805 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