Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Plugin endpoint reachable over the web with no auth or interaction (AV:N/AC:L/PR:N/UI:N); CWE-1284 input-validation flaw enables data tampering only, so I:H with C:N and A:N.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Lifecycle Timeline
1DescriptionCVE.org
Unauthenticated Other Vulnerability Type in WP Travel Engine <= 6.7.10 versions.
AnalysisAI
Improper input validation in the WP Travel Engine WordPress plugin (versions 6.7.10 and earlier) allows remote unauthenticated attackers to tamper with integrity-sensitive data over the network with low complexity. The Patchstack-reported issue carries a CVSS 7.5 driven entirely by high integrity impact (I:H) with no confidentiality or availability effect, and no public exploit identified at time of analysis. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | No special conditions - remote unauthenticated exploitation against default configurations of the WP Travel Engine WordPress plugin at version 6.7.10 or earlier, reachable over HTTP/HTTPS on a publicly accessible WordPress site. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N describes a fully remote, low-complexity, no-auth, no-interaction integrity-only attack - the worst possible exposure profile short of full triad impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker scans the internet for WordPress sites exposing WP Travel Engine endpoints (identifiable via /wp-content/plugins/wp-travel-engine/ asset paths or REST routes) and sends a crafted HTTP request to the vulnerable handler containing malformed quantity or identifier parameters. Because no authentication or user interaction is required, the attacker successfully tampers with stored data - for example, modifying bookings, trip prices, or plugin state - without ever logging in. … |
| Remediation | Upstream fix available per Patchstack; released patched version not independently confirmed in the supplied data - administrators should consult the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-travel-engine/vulnerability/wordpress-wp-travel-engine-plugin-6-7-10-other-vulnerability-type-vulnerability and upgrade WP Travel Engine to the latest version above 6.7.10 via the WordPress plugin dashboard. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Audit all WordPress installations for WP Travel Engine deployment and document affected versions. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36877
GHSA-7cq3-5g9g-7w8q