{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4133 exists.","fix":"No fix has been published for CVE-2025-4133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4133 is a medium-severity cross-site scripting vulnerability in Unknown Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 22 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-4133 and fix it if it is affected.\n\nWhat it is: CVE-2025-4133 is a medium-severity cross-site scripting vulnerability in Unknown Blog2Social: Social Media Auto Post \u0026 Scheduler, published on 22 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4133 exists.\n\nAffected product: Unknown Blog2Social: Social Media Auto Post \u0026 Scheduler. 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-2025-4133/ (Markdown: https://insights.sbomify.com/CVE-2025-4133/index.md)","id":"CVE-2025-4133","markdown":"https://insights.sbomify.com/CVE-2025-4133/index.md","name":"CVE-2025-4133","record":{"aliases":["GHSA-vppg-gg96-53c9"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"low_privilege","summary":"Contributors can inject malicious scripts via post titles in the Blog2Social WordPress plugin dashboard, potentially compromising admin sessions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WPScan","cpe":[{"product":"blog2social","vendor":"adenion"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 Blog2Social: Social Media Auto Post \u0026 Scheduler WordPress plugin before 8.4.0 does not escape the title of posts when outputting them in a dashboard, which could allow users with the contributor role to perform Cross-Site Scripting attacks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Blog2Social: Social Media Auto Post \u0026 Scheduler \u003c 8.4.0 - Contributor+ Stored XSS","id":"CVE-2025-4133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Lack of file validation in Avast Business Antivirus for Linux allows writing untrusted update files","id":"CVE-2025-4134"},"packages":[],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-4132"},"products":["Blog2Social: Social Media Auto Post \u0026 Scheduler"],"published":"2025-05-22","related":[{"cvss_score":9.9,"headline":"Blog2Social: Social Media Auto Post \u0026 Scheduler \u003c= 7.4.1 - Authenticated (Subscriber+) SQL Injection","id":"CVE-2024-3549","kev_date_added":null,"published":"2024-06-11"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-13572","kev_date_added":null,"published":"2019-08-01"},{"cvss_score":8.8,"headline":"Blog2Social \u003c 6.9.10 - Subscriber+ SQLi","id":"CVE-2022-3246","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":8.8,"headline":"Blog2Social: Social Media Auto Post \u0026 Scheduler \u003c 6.3.1 - Authenticated SQL Injection","id":"CVE-2021-24137","kev_date_added":null,"published":"2021-03-18"},{"cvss_score":7.1,"headline":"WordPress Blog2Social Plugin \u003c= 7.2.0 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-40554","kev_date_added":null,"published":"2023-09-06"},{"cvss_score":6.5,"headline":"Blog2Social \u003c 6.9.10 - Subscriber+ SSRF","id":"CVE-2022-3247","kev_date_added":null,"published":"2022-10-25"},{"cvss_score":6.4,"headline":"Cross-site scripting in Blog2Social: Social Media Auto Post \u0026 Scheduler","id":"CVE-2024-7302","kev_date_added":null,"published":"2024-08-01"}],"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-22","vendors":["Unknown"]},"summary":"Contributors can inject malicious scripts via post titles in the Blog2Social WordPress plugin dashboard, potentially compromising admin sessions.","url":"https://insights.sbomify.com/CVE-2025-4133/"}