CVE-2018-10503

CVE-2018-10503 is a high-severity vulnerability in Baijiacms Project Baijiacms with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-352.

Key facts

Description

An issue was discovered in index.php in baijiacms V4 v4_1_4_20170105. CSRF allows adding an administrator account via op=edituser, changing the administrator password via op=changepwd, or deleting an account via op=deleteuser.

Frequently asked questions

What is CVE-2018-10503?
An issue was discovered in index.php in baijiacms V4 v4_1_4_20170105. CSRF allows adding an administrator account via op=edituser, changing the administrator password via op=changepwd, or deleting an account via op=deleteuser.
How severe is CVE-2018-10503?
CVE-2018-10503 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-10503 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (40th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-10503?
CVE-2018-10503 affects Baijiacms Project Baijiacms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-10503?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2018-10503 published?
CVE-2018-10503 was published on 2018-04-27 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Baijiacms Project Baijiacms

All CVEs affecting Baijiacms Project Baijiacms →

Other CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities

Browse all CWE-352 (Cross-Site Request Forgery (CSRF)) vulnerabilities →