CVE-2026-1296
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 Frontend Post Submission Manager Lite plugin for WordPress is vulnerable to Open Redirection in all versions up to, and including, 1.2.7 due to insufficient validation on the 'requested_page' POST parameter in the verify_username_password function. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action such as clicking on a link.
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 Frontend Post Submission Manager Lite WordPress plugin contains an open redirection vulnerability in the verify_username_password function. The 'requested_page' POST parameter is not validated, allowing unauthenticated attackers to craft malicious URLs that redirect users to external sites. This is a medium-severity (CVSS 6.1) issue affecting all versions up to 1.2.7.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Frontend Post Submission Manager Lite' or check the plugins directory for /wp-content/plugins/frontend-post-submission-manager-lite/Affected if The plugin is present on the WordPress site
-
Identify installed versionIn WordPress admin Plugins list, find the plugin and read the version number displayed beneath the plugin name, or inspect the main plugin file header in /wp-content/plugins/frontend-post-submission-manager-lite/fpsml-plugin.phpAffected if Version is 1.2.7 or lower (any version up to and including 1.2.7)
-
Locate vulnerable functionAccess the plugin files via FTP or file manager and locate the verify_username_password function in the plugin code, typically in includes/ajax-handler.php or similar file within the plugin directoryAffected if The function exists and processes the 'requested_page' POST parameter without validation
-
Verify parameter handlingSubmit a test POST request to the plugin's login/verification endpoint (usually the form action URL) with a 'requested_page' parameter set to an external URL (such as https://evil.com) and observe if the application reflects this URL in a redirect responseAffected if The parameter is reflected in Location headers or redirect URLs without validation or restriction to relative paths
A user is affected if the Frontend Post Submission Manager Lite plugin version 1.2.7 or lower is installed and the login/verification form processes the 'requested_page' parameter without validating it is a relative URL.
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 to a patched version when available. Until then, implement server-side validation to restrict the 'requested_page' parameter to relative URLs within the WordPress domain only, rejecting any external or absolute URLs.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1296 — 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-2026-1296 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