CVE-2017-1000011: MyWebSQL version 3.6 is vulnerable to stored XSS in the database manager component resulting in account takeov

Routine

MEDIUM 6.1DOWNGRADE

CVE-2017-1000011 is a medium-severity flaw (CVSS 6.1) affecting mywebsql. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

MyWebSQL version 3.6 is vulnerable to stored XSS in the database manager component resulting in account takeover or stealing of information

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.7% (top 46%)
CISA exploited list	No
Weakness	CWE-79
Published	2017-07-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: mywebsql

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-07-17 13:18 UTCPublished CVE record published
2026-06-17 00:58 UTCUpdated Record last modified

mywebsql mywebsql DOWNGRADE

Affected: 3.6

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.6

1. Check installed version

apt-cache policy mywebsql || rpm -q mywebsql || mywebsql --version

2. No fixed release: DOWNGRADE to a release before 3.6 (Debian / Ubuntu)

apt-cache madison mywebsql sudo apt install mywebsql=<VERSION_BEFORE_3.6> sudo apt-mark hold mywebsql

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mywebsql sudo dnf downgrade mywebsql-<VERSION_BEFORE_3.6> sudo dnf versionlock add mywebsql

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-1000011?

mywebsql: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-1000011 being exploited?

CVE-2017-1000011 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-1000011 affect?

CVE-2017-1000011 affects mywebsql. Severity is medium (CVSS 6.1). MyWebSQL version 3.6 is vulnerable to stored XSS in the database manager component resulting in account takeover or stealing of information

How urgent is CVE-2017-1000011?

Priority 35/100. No elevated risk signals yet.

Related CVEs

CVE-2019-7731 CRITICAL 9.8 DOWNGRADE MyWebSQL 3.7 has a remote code execution (RCE) vulnerability after an attacker writes shell code into the data
CVE-2019-7730 MEDIUM 5.7 DOWNGRADE MyWebSQL 3.7 has a Cross-site request forgery (CSRF) vulnerability for deleting a database via the /?q=wrkfrm&
CVE-2019-7544 MEDIUM 5.4 UPGRADE An issue was discovered in MyWebSQL 3.7

References

← Back to latest CVEs