Html5 MapsWordPress extension · Fla Shop
CVE-2019-5983
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 · uneditedCross-site request forgery (CSRF) vulnerability in HTML5 Maps 1.6.5.6 and earlier allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 confidenceCross-site request forgery (CSRF) vulnerability in the HTML5 Maps WordPress plugin (versions 1.6.5.6 and earlier) allows remote attackers to hijack the authentication of administrators by tricking them into submitting malicious requests while authenticated.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Html5 MapsWordPress extension
<= 1.6.5.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 the installed version of HTML5 Maps pluginIn WordPress admin, go to Plugins > Installed Plugins and locate 'Fla Shop Html5 Maps' or check the plugin directory (wp-content/plugins/html5-maps) for a version file or readme.txtAffected if The version listed is 1.6.5.6 or earlier
-
Verify the exact version number from plugin filesOpen wp-content/plugins/html5-maps/readme.txt and locate the 'Stable tag' entry, or check the main plugin PHP file for a version constantAffected if The stable tag or version constant shows 1.6.5.6 or lower
-
Inspect plugin admin files for CSRF protectionExamine the plugin's admin action handlers (typically in files like admin.php or a class-admin.php) and search for nonce verification calls such as wp_verify_nonce, check_admin_referer, or the presence of 'nonce' fields in formsAffected if No nonce verification is found in state-changing admin operations (settings updates, map edits, data saves)
-
Check form submissions for token presenceLocate any admin forms in the plugin (settings pages, map configuration) and view the HTML source to verify that hidden nonce fields or CSRF tokens are included in the form markupAffected if Forms handling administrative actions lack hidden nonce fields or CSRF tokens
If the installed version is 1.6.5.6 or earlier and the plugin's admin forms lack nonce verification, the environment is affected by this CSRF vulnerability.
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 dataImplement anti-CSRF tokens (synchronizer token pattern) on all state-changing administrative operations and validate Origin/Referer headers to prevent cross-site request forgery attacks.
Fix this in Html5 Maps
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5983 — 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-2019-5983 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