{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-4549 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-4549 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-4549 is a medium-severity cross-site scripting vulnerability in Unknown DoLogin Security, published on 25 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-4549 and fix it if it is affected.\n\nWhat it is: CVE-2023-4549 is a medium-severity cross-site scripting vulnerability in Unknown DoLogin Security, published on 25 Sep 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-4549 in the wild and no public exploit code.\n\nAffected product: Unknown DoLogin Security. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-4549/ (Markdown: https://insights.sbomify.com/CVE-2023-4549/index.md)","id":"CVE-2023-4549","markdown":"https://insights.sbomify.com/CVE-2023-4549/index.md","name":"CVE-2023-4549","record":{"aliases":["GHSA-897r-hcfg-v9vh"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Attackers can inject malicious scripts into the WordPress login form via the X-Forwarded-For header, potentially compromising user sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"dologin_security","vendor":"wpdo"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"The DoLogin Security WordPress plugin before 3.7 does not properly sanitize IP addresses coming from the X-Forwarded-For header, which can be used by attackers to conduct Stored XSS attacks via WordPress' login form.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2023-09-24","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2023-09-24T11:57:46Z","kind":"github_poc","ref":"https://github.com/b0marek/CVE-2023-4549","stars":0,"title":"Repository for CVE-2023-4549 vulnerability. "}],"tier":"poc_unverified"},"has_fix":null,"headline":"DoLogin Security \u003c 3.7 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2023-4549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Unauthenticated Arbitrary File Read","id":"CVE-2023-4550"},"packages":[],"prev":{"headline":"SPA-Cart eCommerce CMS GET Parameter search sql injection","id":"CVE-2023-4548"},"products":["DoLogin Security"],"published":"2023-09-25","related":[{"cvss_score":6.5,"headline":"DoLogin Security \u003c 3.7.1 - Subscriber+ IP Address leak","id":"CVE-2023-4800","kev_date_added":null,"published":"2023-10-16"},{"cvss_score":5.3,"headline":"DoLogin Security \u003c 3.7 - IP Spoofing","id":"CVE-2023-4631","kev_date_added":null,"published":"2023-09-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Unknown"]},"summary":"Attackers can inject malicious scripts into the WordPress login form via the X-Forwarded-For header, potentially compromising user sessions.","url":"https://insights.sbomify.com/CVE-2023-4549/"}